zernio_delete_media
Delete a media file from the Zernio media library by providing its media ID.
Instructions
Delete a media file from the Zernio media library.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mediaId | Yes | The media ID to delete |
Delete a media file from the Zernio media library by providing its media ID.
Delete a media file from the Zernio media library.
| Name | Required | Description | Default |
|---|---|---|---|
| mediaId | Yes | The media ID to delete |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. The description does not disclose if deletion is permanent, reversible, or what side effects occur (e.g., breaking references). Lacks behavioral context beyond the obvious delete action.
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?
Single concise sentence with no extraneous words. Efficiently communicates purpose.
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?
Minimal for a tool with no output schema and no annotations. Does not specify return value, success/failure, or additional behavior. Misses opportunity to guide agent on expected outcomes.
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 describes parameter adequately ('The media ID to delete'). Description adds no extra meaning beyond the schema. With 100% coverage, baseline is 3.
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?
The description clearly states the action ('Delete'), the resource ('a media file'), and the context ('from the Zernio media library'). It is specific and distinguishes from sibling delete tools by specifying 'media file'.
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 tool versus alternatives like zernio_delete_post or zernio_delete_comment. No mention of prerequisites, limitations, or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Eyalm321/zernio-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server