Skip to main content
Glama

Write an asset onto a plan

create_content_item

Create a copy/image/email asset with the text you supply, attached to an existing plan. This is the override path: the planner does not write the copy, but the asset still inherits the plan's brief. Nothing is published.

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": {
      "plan_id": "<plan_id>",
      "caption": "<caption>"
    },
    "name": "create_content_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNocopy
statusNodraft
captionYesThe post text itself
plan_idYes
hashtagsNo
social_account_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Adds real context beyond the annotations: the asset inherits the plan's brief, and 'Nothing is published' bounds the side effect of a non-readOnly, non-idempotent write. It says nothing about whether repeated calls duplicate the asset (the idempotentHint=false case) or what permissions/ownership apply.

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?

Three tight sentences, front-loaded with the creation action and followed by the distinguishing 'override path' rationale. No filler, though the third fragment ('Nothing is published.') could be folded into the scope sentence.

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?

A write tool with six parameters, 17% schema coverage, and no output schema needs the description to fill more gaps than it does—notably the significance of status and what identifier comes back. The brief-inheritance and no-publish notes are the right kind of content, just insufficient for the schema gaps.

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?

With only 17% schema description coverage, the description must carry the parameters, but it only loosely implies plan_id ('attached to an existing plan') and caption ('the text you supply'). status (draft vs approved), hashtags, and social_account_id go entirely unexplained, and the type enum is only partially mirrored as 'copy/image/email'.

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?

Specific verb ('Create') plus resource ('copy/image/email asset ... attached to an existing plan'), and the 'override path' framing distinguishes it from planner-generated assets. It stops short of separating it explicitly from siblings like create_post_draft, so an agent must still infer the copy-path boundary.

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

Usage Guidelines4/5

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

'This is the override path: the planner does not write the copy' clearly signals the condition that selects this tool over the planner-driven flow. No alternatives are named and there is no explicit when-not guidance (e.g., versus drafting or scheduling), leaving some inference.

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