list_mediaList uploaded media assets with IDs, type, dimensions, and post reference counts. Filter by image or video to find assets used in social posts.
List uploaded media assets with their ids, type, dimensions, and how many posts reference them.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | ||
| limit | No | ||
| cursor | No |
Changes observed during successful MCP inspections.
v0.3.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful fact that reference counts are returned, but omits pagination behavior despite a cursor parameter.
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?
A single front-loaded sentence with zero filler; the listing purpose and payload contents come before anything else.
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, 0% parameter coverage, and a cursor-based pagination parameter, the description should explain filtering and paging semantics. It leaves the agent unable to determine how to narrow or page results.
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%, so the description carries the burden for all three parameters, yet it explains none of them. The word "type" in the description refers to a returned field's type, which is ambiguous against the 'type' enum filter parameter, and limit/cursor are never addressed.
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 (list) and resource (uploaded media assets) and enumerates the returned fields. It is clearly distinguishable from the singular get_media sibling, though it does not name that sibling explicitly to reinforce the split.
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?
No guidance on when to use this versus get_media or upload_media, and no mention that the type filter or cursor pagination exist. The agent must infer usage entirely.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.