Skip to main content
Glama

prismic_get_releases

Retrieve release references from Prismic Content API to access and analyze content snapshots for specific releases, enabling structured content inspection.

Instructions

Get release refs from Content API root.

Returns non-master refs only, equivalent to filtering repository refs by isMasterRef != true. Use these refs with read tools (ref parameter) to inspect release content through Content API. Note: querying documents with a release ref returns a content snapshot at that ref, not only the release "planned items" shown in Prismic UI. Efficiency tip: pick the release ref once and reuse it across all read queries in the same analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation handler for the prismic_get_releases tool.
    async def handle_prismic_get_releases(
        *,
        service_factory: ServiceFactory = _build_service,
    ) -> dict[str, Any]:
        """Return release refs (non-master refs) from Prismic Content API root."""
    
        async with service_factory() as service:
            releases = await service.get_releases()
    
        return {"releases": releases}
  • The registration of the prismic_get_releases tool using the @server.tool decorator.
    @server.tool(name="prismic_get_releases")
    async def prismic_get_releases() -> dict[str, Any]:
        """Get release refs from Content API root.
    
        Returns non-master refs only, equivalent to filtering repository refs by
        `isMasterRef != true`.
        Use these refs with read tools (`ref` parameter) to inspect release
        content through Content API.
        Note: querying documents with a release `ref` returns a content snapshot
        at that ref, not only the release "planned items" shown in Prismic UI.
        Efficiency tip: pick the release `ref` once and reuse it across all read
        queries in the same analysis.
        """
    
        return await handle_prismic_get_releases()
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 and does well by disclosing key behavioral traits: it's a read-only operation (implied by 'Get' and usage with 'read tools'), returns a filtered subset of refs, and clarifies that querying with release refs returns a content snapshot (not just planned items). It also provides an efficiency tip. However, it doesn't mention potential errors, rate limits, or authentication needs, leaving some gaps.

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 front-loaded with the core purpose, followed by clarifications and usage tips in a logical flow. Every sentence adds value: the first states what it does, the second clarifies the output, the third explains usage, the fourth warns about content interpretation, and the fifth provides an efficiency tip. No wasted words.

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

Completeness5/5

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

Given the tool's complexity (simple read operation with 0 parameters), no annotations, and the presence of an output schema (which handles return values), the description is complete enough. It covers purpose, output filtering, usage context, behavioral nuances (content snapshot vs. planned items), and efficiency advice, leaving no significant gaps for the agent.

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

Parameters4/5

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

The tool has 0 parameters, with 100% schema description coverage. The description adds no parameter information, which is appropriate. A baseline of 4 is applied for zero-parameter tools, as there's no need to compensate for schema gaps, and the description focuses on usage context instead.

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 clearly states the specific action ('Get release refs'), resource ('from Content API root'), and scope ('non-master refs only'), distinguishing it from sibling tools like prismic_get_refs (which presumably includes master refs). It provides a precise technical equivalent ('filtering repository refs by `isMasterRef != true`).

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool ('Use these refs with read tools (`ref` parameter) to inspect release content through Content API') and provides an efficiency tip for reuse. It implicitly distinguishes from alternatives by specifying it returns 'non-master refs only,' contrasting with tools that might handle master refs or other content types.

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