Skip to main content
Glama

ADS Beast

seo_content_write

Writes search- and AI-citation-ready content on a topic and saves it as a draft. Takes up to a minute. AI: 1 AI request. May return a job_id (get_job_result).

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": {
      "topic": "<topic>"
    },
    "name": "seo_content_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
geoNoCountry code, e.g. us or de.
topicYesTopic, product or service.
client_idNo
word_countNoTarget length in words.
content_typeNoblog_post, landing_page, guide, faq_page or case_study.blog_post

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, but the description adds genuinely new behavior: the result is saved as a draft (nothing is published), the call can take up to a minute, and it consumes one AI request. The async hint ("May return a job_id (get_job_result)") tells the agent to expect a possible deferred result, which annotations alone would not reveal.

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?

Three short, front-loaded fragments with zero filler: what it does, how long it takes, what it costs, and how to handle a job_id. Every clause earns its place and the most decision-relevant facts come first.

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?

With no output schema, the description correctly discloses the key return behavior (draft saved, possible job_id plus the follow-up tool) and latency/cost. It leaves minor gaps, such as where the draft is saved and whether content is returned inline, but the essentials for calling it correctly are 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 80%, so the schema already documents geo, topic, word_count and content_type (including enum values). The description only echoes 'topic' and adds no syntax, constraint, or selection guidance for parameters such as client_id, which is undocumented in both places. Baseline 3 applies when the schema carries the weight.

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 gives a specific verb and output ("Writes search- and AI-citation-ready content on a topic and saves it as a draft"), so an agent knows exactly what is produced and that it is a draft rather than a publish. It does not distinguish itself from near-neighbours like seo_article_generate or seo_brief_generate, so the sibling differentiation element is missing.

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

Usage Guidelines3/5

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

Usage is only implied by the phrasing (write content on a topic). There is no explicit when-to-use statement, no exclusions, and no comparison to the many adjacent generation tools in the sibling list. The only real routing guidance is the follow-up hint that a job_id may be returned and should go to get_job_result.

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.