Agentic CMS

attach_gallery_media

Attach existing media to a gallery item with a role and sort order. Links cover, gallery, detail, or hero video media for CMS content management.

Instructions

Attach an existing media row to a gallery item with role + sort_order. role defaults to gallery.

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": {
      "item_id": "<item_id>",
      "media_id": "<media_id>"
    },
    "name": "attach_gallery_media"
  }
}

Input Schema

Name	Required	Description
`role`	No	Role (default 'gallery')
`item_id`	Yes
`media_id`	Yes
`sort_order`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses only the role default. It does not say whether attaching is idempotent, whether the same media can be attached twice, what happens to existing sort_order values, or what permissions are required for this mutation.

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?

Two tight sentences with zero filler, leading with the action and following with the default behavior. Every clause earns its place.

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

Completeness2/5

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

A mutation tool with no annotations, no output schema, and two undocumented required parameters needs more than two sentences. Nothing covers idempotency, duplicate handling, ordering semantics, or the return value, so an agent cannot reliably predict the effect of a call.

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 coverage is only 25% (just the role field), so the description must compensate; it does explain role and its 'gallery' default and mentions sort_order. However, the two required UUID parameters (item_id, media_id) are entirely undocumented and the description never explains what sort_order actually orders, leaving a real gap.

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?

Clear verb+resource: 'Attach an existing media row to a gallery item', naming both the media-side and gallery-side entities. It implicitly distinguishes itself from detach_gallery_media and set_gallery_cover via the 'attach' verb and generic role handling, though it never states the distinction explicitly.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as set_gallery_cover (which sets the cover role) or how this relates to list_gallery_media/detach_gallery_media. Usage is only inferable from the verb.

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

Deploy Server