Marketing Assistant MCP

Overview Schema Source Related Servers Discussions Admin

Approve draft post

approve_draft

Approve a draft for publication after human review. Only approved drafts can be published, ensuring content is authorized before posting.

Instructions

Mark a draft as approved by the human user. Only approved drafts can be published. Only call this after the user has explicitly reviewed and approved the draft text.

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": {
      "id": "<id>"
    },
    "name": "approve_draft"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Draft id.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jul 31, 2026

TDQS

A4/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 adds a key prerequisite ('after the user has explicitly reviewed and approved') and a system rule ('Only approved drafts can be published'). However, it does not disclose whether the operation is reversible, what happens if the draft is already approved, or any error conditions, leaving some behavioral gaps.

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?

The description is two concise sentences with a clear action-first structure. Every sentence provides meaningful context: the first defines the action, the second adds a usage condition and system implication. No unnecessary words.

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

Completeness4/5

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

For a simple state-change tool with one parameter and no output schema, the description covers the essential aspects: what it does, when to call it, and why it matters. It could add details about edge cases or effects on the draft object, but this is a low-complexity tool where the description is largely sufficient.

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?

The input schema already fully describes the single 'id' parameter as 'Draft id', and the description does not add any additional meaning or context for the parameter. With 100% schema coverage, the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Mark') and resource ('draft as approved'), which is specific and distinguishes it from siblings like reject_draft and publish_draft. It is unambiguous about the action being an approval state change.

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?

The description gives a clear condition: 'Only call this after the user has explicitly reviewed and approved the draft text.' It also implies a relationship with publish_draft by noting that only approved drafts can be published, which helps the agent sequence actions. It does not explicitly mention alternatives like reject_draft, but the context is sufficient for most scenarios.

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