Skip to main content
Glama
Doist
by Doist

fetch-object

Read-onlyIdempotent

Retrieve full details of a specific task, project, comment, or section by ID. Optionally include direct subtasks or sub-projects to check for hidden children.

Instructions

Fetch a single task, project, comment, or section by its ID. Use this when you have a specific object ID and want to retrieve its full details. Set includeChildren to also get its direct subtasks or sub-projects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe unique ID of the object to fetch.
typeYesThe type of object to fetch.
includeChildrenNoAlso return the direct children of the object: subtasks for a task, sub-projects for a project. Returns childCount plus a compact list, flagging each child that has children of its own. Use this to check whether a task hides subtasks instead of a speculative find-tasks lookup. Ignored for comments and sections.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the fetched object.
typeYesThe type of object fetched.
objectYesThe fetched object data.
childrenNoDirect children only: subtasks for a task, sub-projects for a project. Completed subtasks and archived sub-projects are excluded.
childCountNoThe number of direct children listed in children. Only present when children were requested and the type supports them. 0 means the object definitively has none.
childrenErrorNoPresent when the children lookup failed or returned incomplete information. When no children are listed alongside it, childCount is unknown - do not read its absence as "no children".
hasMoreChildrenNoPresent when the object has more than 25 direct children and the list was truncated. Page through the rest with find-tasks by parentId for subtasks, or find-projects for sub-projects.
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds meaningful context about object types, full-detail retrieval, and optional child inclusion, which complements rather than contradicts the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two front-loaded sentences with no redundancy. Every clause adds value: single object, supported types, ID-based retrieval, and optional child behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple single-object fetch operation, rich parameter schema, and available output schema, the description plus structured metadata provides complete context for correct tool selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and parameter descriptions already explain id, type, and includeChildren behavior. The description reinforces includeChildren but does not add meaning materially beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific action ('Fetch a single task, project, comment, or section by its ID'), which distinguishes it from sibling find/list tools that search rather than retrieve by known ID.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance: 'Use this when you have a specific object ID and want to retrieve its full details.' The includeChildren parameter description also steers users away from a speculative find-tasks lookup, though it does not explicitly enumerate exclusions for alternate use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Doist/todoist-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server