list_media_foldersList the account's media folders.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | One row per media folder — id and name. | |
| meta | No | Pagination for the list — page, limit and the total row count. | |
| success | Yes | True when the call succeeded. A failure comes back as an error result instead. |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "data": {
+ "description": "One row per media folder — id and name.",
+ "items": {},
+ "type": "array"
+ },
+ "meta": {
+ "additionalProperties": true,
+ "description": "Pagination for the list — page, limit and the total row count.",
+ "properties": {
+ "limit": {
+ "description": "Maximum rows per page.",
+ "type": "number"
+ },
+ "page": {
+ "description": "Zero-based index of the page returned.",
+ "type": "number"
+ },
+ "total": {
+ "description": "Total rows matching the query across all pages.",
+ "type": "number"
+ }
+ },
+ "type": "object"
+ },
+ "success": {
+ "description": "True when the call succeeded. A failure comes back as an error result instead.",
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "success"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the account-level scope and does not contradict the annotations, but it does not disclose ordering, pagination, or other behavior. Given the output schema, the missing details are not critical.
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 sentence that front-loads the verb and resource with no filler. Every word earns its place.
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?
For a zero-parameter read-only tool with an output schema and annotations covering safety, the description fully specifies what the tool does. Nothing required to invoke it correctly is missing.
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?
The tool accepts zero parameters, so there is nothing for the description to add beyond the schema. The baseline of 4 applies because no parameter documentation is needed.
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'), resource ('media folders'), and scope ('the account's'). It is distinct from sibling tools by naming the media-folder resource rather than generic folders or media files.
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?
The phrase 'the account's media folders' gives clear context for when this tool is the right choice: when the agent needs the account's set of media folders. It does not explicitly exclude alternatives like list_media or list_folders, but for a zero-parameter read-only list that omission is minor.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.