Agentic CMS

create_publication

Record where and when content was published, including channel, URL, and variant details, so publication history and variant-level metrics stay traceable.

Instructions

[Pipeline step 6 — Publish tracking] Record a publication event (where/when the content went out). Include variant_id so the Content detail view traces which variant was published on which channel. Final pipeline step — after this use get_metrics + get_activity_logs for feedback loop.

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": {
      "content_id": "<content_id>",
      "channel": "<channel>"
    },
    "name": "create_publication"
  }
}

Input Schema

Name	Required	Description
`url`	No	URL where the content was published
`channel`	Yes	Publication channel (e.g., "blog", "twitter", "linkedin")
`metrics`	No	Initial metrics (views, clicks, etc.)
`content_id`	Yes	ID of the content that was published
`variant_id`	No	Optional variant that was actually published (recommended when a specific platform variant is being recorded — enables variant-level metric tracking).
`channel_post_id`	No	Platform-specific post ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses sequencing (final step, follow-up tools) and the side benefit of variant_id for downstream tracing, but says nothing about whether records are immutable, whether duplicate publishes are allowed, required permissions, or what is returned on success.

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 dense sentences with the pipeline position front-loaded and no filler; the bracketed label is slightly redundant with the title-less name but still scannable.

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?

For a 6-parameter mutation tool with no annotations and no output schema, the description covers workflow position and follow-up tools but omits the success/return shape, idempotency, and error behavior an agent would want before invoking it.

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 100%, so the schema already documents all six parameters, including variant_id's 'enables variant-level metric tracking' rationale. The description only adds the Content detail view tracing angle for variant_id, which is marginal beyond the schema baseline.

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?

States a specific verb and resource ('Record a publication event') and qualifies it with the where/when scope, so the agent knows this is event logging rather than content creation (create_content) or variant creation (create_variant). It does not explicitly name a sibling it should be chosen over, so it falls short of a 5.

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?

Explicitly places the tool as 'Pipeline step 6' and the 'Final pipeline step', and tells the agent exactly what to do next (get_metrics + get_activity_logs for the feedback loop). That is real routing guidance, though there is no explicit when-not-to-use condition.

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

Deploy Server