Skip to main content
Glama

prismic_insert_shared_slice

Insert a new Shared Slice model into Prismic by providing a complete JSON model, enabling structured content creation through the Prismic Content MCP server.

Instructions

Insert a new Shared Slice model.

Uses POST /slices/insert. Pass a full Shared Slice JSON model.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
shared_sliceYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual handler function that implements the logic for inserting a shared slice by calling the service.
    async def handle_prismic_insert_shared_slice(
        *,
        shared_slice: dict[str, Any],
        service_factory: ServiceFactory = _build_service,
    ) -> dict[str, Any]:
        """Insert a Shared Slice model via Prismic Custom Types API."""
    
        async with service_factory(require_write_credentials=True) as service:
            result = await service.insert_shared_slice_model(shared_slice=shared_slice)
    
        return result
  • The tool registration decorator and wrapper function that invokes the handler.
    @server.tool(name="prismic_insert_shared_slice")
    async def prismic_insert_shared_slice(shared_slice: dict[str, Any]) -> dict[str, Any]:
        """Insert a new Shared Slice model.
    
        Uses `POST /slices/insert`.
        Pass a full Shared Slice JSON model.
        """
    
        return await handle_prismic_insert_shared_slice(shared_slice=shared_slice)
Behavior2/5

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

With no annotations, the description carries full burden but provides minimal behavioral insight. It mentions the HTTP method ('POST') and that a 'full JSON model' is required, but lacks details on permissions, side effects, error handling, or response format, which are critical for a mutation tool.

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

Conciseness4/5

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

The description is brief and front-loaded with the main action, using three sentences efficiently. However, the second sentence about the HTTP method could be integrated more smoothly, and some redundancy exists between 'Insert' and 'POST'.

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?

Given the tool's complexity (mutation with nested objects) and lack of annotations, the description is incomplete. It mentions the output schema exists but doesn't explain return values or error cases. For a creation tool, more context on success/failure outcomes is needed.

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?

Schema description coverage is 0%, but the description adds some value by specifying 'Pass a full Shared Slice JSON model', clarifying the parameter's purpose. However, it doesn't detail the JSON structure, required fields, or examples, leaving significant gaps in understanding.

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 ('Insert') and resource ('Shared Slice model'), making the purpose understandable. It distinguishes from siblings like 'prismic_update_shared_slice' by specifying 'new', but doesn't explicitly contrast with all alternatives like 'prismic_get_shared_slice'.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. While 'new' implies creation rather than updating, there's no mention of prerequisites, constraints, or specific scenarios for insertion versus other operations like 'prismic_insert_custom_type'.

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