List images and PDFs in a RedStudio customer's media library and return public URLs for embedding in page HTML. Use it to find existing assets before publishing or editing pages.
List the customer media library (images, PDFs) with public URLs to use in page HTML.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It usefully discloses that returned entries include public URLs suitable for page HTML, which is real behavioral context. It does not state pagination, ordering, size limits, or whether the operation is read-only (though 'List' strongly implies it).
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 no filler. Every clause (library scope, content types, public URL return, intended use) 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 tool with no output schema, the description covers what the tool returns (media with public URLs) and why it matters. It stops short of describing result shape or pagination, but nothing critical for invoking it 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 takes zero parameters, so the baseline is 4. The schema is empty and the description correctly indicates no filtering input is required or offered.
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 (customer media library), and adds scope detail by naming the content types (images, PDFs). This clearly separates it from upload_media and delete_media siblings, though it does not explicitly name them.
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 'to use in page HTML' implies the context in which this list is needed, giving implied usage guidance. However, there is no explicit when-to-use versus when-not, and no mention of alternatives such as fetching a single item.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.