Skip to main content
Glama
Sign In
@lapage/strapi-mcp

@lapage/strapi-mcp

by zhuylanz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

strapi_get_media

Retrieve a specific Strapi media file by its file ID to access individual media assets directly.

Instructions

Get one Strapi Media Library file by file id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "fileId": "<fileId>"
    },
    "name": "strapi_get_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileIdYesNumeric Strapi upload file id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must disclose behavioral traits. It only states the operation and does not describe return format, error behavior, or whether it's read-only. While 'get' implies read-only, the description lacks any explicit caveats or outcome details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no redundancy. It communicates the core action and parameter efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter getter, the description provides basic understanding, but with no output schema or behavioral detail, the agent cannot know what the response will contain (e.g., metadata vs binary) or failure handling. This leaves a gap in completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema fully documents the sole parameter (fileId) with type and description. The description simply reinforces 'by file id' without adding new semantic details, so it meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'Get' and resource 'one Strapi Media Library file by file id', clearly distinguishing it from sibling tools like strapi_list_media (list all files) and strapi_upload_media_from_url (upload). It fully states the tool's purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or alternative guidance is given. The usage is implied by the name and description (fetch a single media file by ID vs listing via strapi_list_media), but there is no explicit mention of when to prefer this over other tools or any exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools