Retrieve a paginated list of previously created text-to-texture tasks via the Meshy AI API, sortable by creation date ascending or descending.
List previously created text-to-texture tasks via the /v1/retexture API. sort_by accepts '+created_at' or '-created_at'.
| Name | Required | Description | Default |
|---|---|---|---|
| sort_by | No | ||
| page_num | No | ||
| page_size | No |
Changes observed during successful MCP inspections.
v1.2.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It never states the default sort order, default page size, maximum page size, whether results are scoped to the caller's account, or how an empty result is represented — all material for a paginated read tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, front-loaded with the action and resource. The second sentence partly duplicates the schema enum, which keeps it from being maximally efficient, but there is no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and no annotations, the description is the only source of behavior, yet it omits pagination semantics, result shape, and ordering defaults. For a paginated list tool in a crowded sibling family, this leaves the agent guessing on essentials.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% across 3 parameters. The description spells out sort_by values, which largely repeats the enum in the schema, while page_num and page_size receive no defaults, ranges, or size limits at all.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('List previously created text-to-texture tasks'), which is unambiguous on its own. However, it adds 'via the /v1/retexture API', an implementation detail that collides conceptually with the sibling list_retexture_tasks and provides no differentiation between the two.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no statement of when to use this list tool rather than retrieve_text_to_texture_task, stream_text_to_texture_task, or the near-identical list_retexture_tasks. Usage is only implied by the verb 'List', leaving the agent to infer the routing in a family of ~50 siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.