Skip to main content
Glama

prismic_get_media

Retrieve media assets from Prismic's Asset API using filters like asset type, keywords, and pagination controls to manage digital content.

Instructions

List media assets from Prismic Asset API.

This maps directly to GET /assets query parameters: assetType, limit, cursor, and keyword. Requires PRISMIC_REPOSITORY and PRISMIC_WRITE_API_TOKEN.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asset_typeNo
limitNo
cursorNo
keywordNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler implementation for the `prismic_get_media` tool, which calls the service to list assets from the Prismic Asset API.
    async def handle_prismic_get_media(
        *,
        asset_type: str | None = None,
        limit: int | None = None,
        cursor: str | None = None,
        keyword: str | None = None,
        service_factory: ServiceFactory = _build_service,
    ) -> dict[str, Any]:
        """List assets from the Prismic Asset API (`GET /assets`)."""
    
        async with service_factory() as service:
            media = await service.get_media(
                asset_type=asset_type,
                limit=limit,
                cursor=cursor,
                keyword=keyword,
            )
    
        return {"media": media}
  • The tool registration for `prismic_get_media` using the FastMCP decorator.
    @server.tool(name="prismic_get_media")
    async def prismic_get_media(
        asset_type: str | None = None,
        limit: int | None = None,
        cursor: str | None = None,
        keyword: str | None = None,
    ) -> dict[str, Any]:
        """List media assets from Prismic Asset API.
    
        This maps directly to `GET /assets` query parameters:
        `assetType`, `limit`, `cursor`, and `keyword`.
        Requires `PRISMIC_REPOSITORY` and `PRISMIC_WRITE_API_TOKEN`.
        """
    
        return await handle_prismic_get_media(
            asset_type=asset_type,
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively communicates that this is a read operation ('List'), maps to a specific API endpoint, and discloses authentication requirements (PRISMIC_REPOSITORY and PRISMIC_WRITE_API_TOKEN). It doesn't mention rate limits, pagination behavior beyond cursor usage, or error conditions, but provides solid foundational context.

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 perfectly front-loaded with the core purpose in the first sentence, followed by essential implementation details. Every sentence earns its place: the first establishes what the tool does, the second maps parameters to the API, and the third states authentication requirements. No wasted words or redundancy.

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

Completeness4/5

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

For a read operation with 4 parameters and an output schema (which handles return values), the description provides good context: purpose, parameter mapping, and authentication. It doesn't mention pagination strategy (cursor usage) or potential response formats, but with an output schema available, those details are less critical. The main gap is lack of error handling or rate limit information.

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

Parameters5/5

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

Given 0% schema description coverage (titles like 'Asset Type' and 'Limit' provide minimal semantic value), the description adds crucial meaning by explicitly naming all four parameters (assetType, limit, cursor, keyword) and clarifying they map directly to GET /assets query parameters. This transforms completely undocumented parameters into well-understood API arguments.

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

Purpose4/5

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

The description clearly states the action ('List media assets') and resource ('from Prismic Asset API'), making the purpose immediately understandable. It distinguishes this tool from siblings like prismic_add_media (which creates rather than lists) and prismic_get_document (which fetches documents rather than media assets). However, it doesn't explicitly contrast with all similar retrieval tools like prismic_get_custom_types.

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?

The description implies usage context by mentioning it maps to GET /assets and requires specific credentials, suggesting when authentication is needed. However, it doesn't provide explicit guidance on when to use this tool versus alternatives like prismic_get_documents or prismic_get_shared_slices, nor does it mention any exclusions or prerequisites beyond the credentials.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rahulpowar/prismic-content-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server