read_v2_task_logs
Returns authorized lifecycle events and available bounded native output. Continue with the response's event and character positions. A task family without native output can still expose events.
These signatures come from local MCP tool discovery. Use the signature registered by your deployment and confirm your identity and permissions before calling the tool.
Endpoint signatures and example arguments
Examples show the arguments to the tool. Replace placeholder IDs and illustrative revisions with values from your authorized disposable scope.
Bound application
Page authorized lifecycle diagnostics and native bounded task output.
- Required arguments
task_id- Optional arguments
after_event,event_limit,after_character,character_limit
{
"task_id": "{{task_id}}",
"after_event": 0,
"event_limit": 25,
"after_character": 0,
"character_limit": 4096
}
Exact JSON input schema
{
"properties": {
"task_id": {
"title": "Task Id",
"type": "string"
},
"after_event": {
"default": 0,
"title": "After Event",
"type": "integer"
},
"event_limit": {
"default": 100,
"title": "Event Limit",
"type": "integer"
},
"after_character": {
"default": 0,
"title": "After Character",
"type": "integer"
},
"character_limit": {
"default": 16384,
"title": "Character Limit",
"type": "integer"
}
},
"required": [
"task_id"
],
"title": "read_v2_task_logsArguments",
"type": "object"
}
Application router
Page authorized lifecycle diagnostics and native bounded task output.
- Required arguments
workspace_id,application_id,task_id- Optional arguments
after_event,event_limit,after_character,character_limit
{
"workspace_id": "{{workspace_id}}",
"application_id": "operating-cube",
"task_id": "{{task_id}}",
"after_event": 0,
"event_limit": 25,
"after_character": 0,
"character_limit": 4096
}
Exact JSON input schema
{
"properties": {
"workspace_id": {
"title": "Workspace Id",
"type": "string"
},
"application_id": {
"title": "Application Id",
"type": "string"
},
"task_id": {
"title": "Task Id",
"type": "string"
},
"after_event": {
"default": 0,
"title": "After Event",
"type": "integer"
},
"event_limit": {
"default": 100,
"title": "Event Limit",
"type": "integer"
},
"after_character": {
"default": 0,
"title": "After Character",
"type": "integer"
},
"character_limit": {
"default": 16384,
"title": "Character Limit",
"type": "integer"
}
},
"required": [
"workspace_id",
"application_id",
"task_id"
],
"title": "read_v2_task_logsArguments",
"type": "object"
}
Handling errors
MCP_TOOL_CAPACITY_NOT_DISPATCHED means the server did not dispatch this call. MCP_TOOL_DEADLINE_OUTCOME_UNKNOWN or MCP_TOOL_PROCESS_FAILED_OUTCOME_UNKNOWN leaves the outcome unknown. For a call with effects, reconcile the original request before starting a new one. For a scoped denial, verify the caller's grant and the selected target.
Module guidelines Β· Related workflow Β· Application-language function catalog