Skip to main content
Glama

Add collection content

add_collection_content
Idempotent

Adds published, visible Library content to a collection or one of its sections.

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": {
      "idempotency_key": "<idempotency_key>",
      "collection_id": "<collection_id>",
      "expected_revision": "<expected_revision>",
      "content": "<content>"
    },
    "name": "add_collection_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes
section_idNo
collection_idYes
idempotency_keyYes
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive, idempotent write with no open-world access, so the safety profile is covered. The description usefully adds the constraint that only published, visible Library content qualifies, but says nothing about what happens on revision conflict, whether content is appended or merged, or the 29-item cap.

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?

A single front-loaded sentence with no wasted words, and the key eligibility constraint is stated immediately. It is arguably too terse for a five-parameter mutation, but nothing in it is redundant.

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?

For a mutation tool with 5 parameters, 4 required, zero schema descriptions, and no output schema, one sentence is not enough. Key operational details, notably optimistic concurrency via expected_revision and idempotency behavior, are absent.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the burden, yet it only loosely maps to collection_id and section_id via 'a collection or one of its sections'. The required idempotency_key, expected_revision, and the content array's content_type/content_id structure are entirely unexplained.

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 names a specific verb ('Adds') and resource ('Library content' into a 'collection or one of its sections'), and adds a meaningful qualifier that only published, visible content can be added. It does not distinguish this from siblings such as attach_lesson_content or import_library_content, which an agent must resolve on its own.

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?

There is no when-to-use or when-not-to-use guidance and no comparison to alternative tools that also place content somewhere. The description also omits prerequisites implied by the required parameters, such as needing a current expected_revision or an idempotency key before calling.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources