Skip to main content
Glama

prismic_update_shared_slice

Modify an existing Shared Slice model in Prismic by providing the updated JSON structure for content management.

Instructions

Update an existing Shared Slice model.

Uses POST /slices/update. Pass the full updated Shared Slice JSON model.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
shared_sliceYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the logic for updating a Shared Slice.
    async def handle_prismic_update_shared_slice(
        *,
        shared_slice: dict[str, Any],
        service_factory: ServiceFactory = _build_service,
    ) -> dict[str, Any]:
        """Update a Shared Slice model via Prismic Custom Types API."""
    
        async with service_factory(require_write_credentials=True) as service:
            result = await service.update_shared_slice_model(shared_slice=shared_slice)
    
        return result
  • The tool registration and entry point for prismic_update_shared_slice.
    @server.tool(name="prismic_update_shared_slice")
    async def prismic_update_shared_slice(shared_slice: dict[str, Any]) -> dict[str, Any]:
        """Update an existing Shared Slice model.
    
        Uses `POST /slices/update`.
        Pass the full updated Shared Slice JSON model.
        """
    
        return await handle_prismic_update_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 states the tool updates a model and uses a POST endpoint, but doesn't disclose permissions, side effects, rate limits, or response format. This is inadequate for a mutation tool with zero annotation coverage.

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 two sentences that directly state the action and parameter. There's no wasted text, but it could be more structured with bullet points or examples for better clarity.

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 complexity (mutation tool with nested objects) and no annotations, the description is incomplete. It mentions the output schema exists but doesn't explain return values or error handling. For a tool updating a shared slice, more context on behavior and parameters 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%, so the description must compensate. It adds that the parameter is 'the full updated Shared Slice JSON model', giving basic semantics beyond the schema's generic object type. However, it doesn't detail structure, fields, or constraints, leaving significant gaps.

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 ('Update') and resource ('existing Shared Slice model'), making the purpose evident. It distinguishes from siblings like 'prismic_insert_shared_slice' by specifying 'existing' versus creation, though it doesn't explicitly name alternatives. This is specific but could be more distinct.

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. It mentions the HTTP method ('POST /slices/update') but doesn't clarify prerequisites, such as needing an existing slice, or contrast with tools like 'prismic_update_custom_type'. Usage is implied by the action but lacks explicit context.

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