Skip to main content
Glama

ADS Beast

prepare_article_distribution

Prepare drafting social posts that announce a blog article of a client on the chosen channels. Changes nothing: stores a preview_id (15 min, single use) to show, then execute_prepared_change.

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": {
      "article_id": "<article_id>",
      "channels": "<channels>",
      "reason": "<reason>"
    },
    "name": "prepare_article_distribution"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesWhy, with numbers (shown to the approver).
channelsYesChannels to draft posts for.
article_idYesADS Beast article id, as returned by seo_article_generate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description discloses the key behavioral traits: nothing external changes, a preview_id is stored, it expires in 15 minutes, and it is single-use. That is exactly the hidden state machine an agent needs and cannot get from the annotations.

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?

Two tight sentences: the first states the purpose, the second explains the non-destructive preview/execute handoff. The phrasing 'Prepare drafting social posts that announce a blog article of a client on the chosen channels' is slightly convoluted but no sentence is wasted.

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 three-required-parameter tool with no output schema, the description covers what matters most: what it produces (a short-lived preview_id) and the follow-up step. It could say more about what a preview contains or what happens if the preview expires unused, but the essential contract is present.

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% and every parameter (article_id, channels, reason) is already documented in the schema, including the enum values for channels and the note that reason is shown to the approver. The description adds no per-parameter meaning beyond that, so the baseline of 3 applies.

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 names a specific action (prepare/draft social posts announcing a blog article) and scope (chosen channels), and it explicitly positions itself as the step before execute_prepared_change, so an agent can distinguish it from the many other prepare_* siblings and from execute_prepared_change itself.

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?

It clearly signals the intended usage pattern: call this first to get a preview_id, then call execute_prepared_change to actually apply it. It does not spell out when not to use it (e.g., if a preview already exists, or for scheduling rather than drafting, which prepare_social_post_schedule might cover), so guidance is strong but not exhaustive.

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.