Skip to main content
Glama

ADS Beast

seo_article_generate

Writes an SEO article for a keyword and saves it as a draft. Nothing is published. Takes up to a minute. AI: 1 AI request.

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": {
      "keyword": "<keyword>",
      "client_id": "<client_id>"
    },
    "name": "seo_article_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYesTarget search query.
client_idYes
word_countNoTarget length in words.

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?

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, and the description adds genuinely useful context: the output is a saved draft, nothing is published, it can take up to a minute, and it consumes one AI request. That disclosure of latency, cost, and mutation outcome is valuable. It falls short of a 4 because it never says where the draft is saved or what happens on failure (for example, whether a partial draft is left behind), which matters for a write operation.

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?

Four short, front-loaded sentences with no filler; the effect ("saves it as a draft; nothing is published") is stated before the operational cost details. Slight redundancy between the title and the first clause, but nothing wasted.

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 three-parameter write tool with no output schema, the definition covers outcome and cost but not the return value (article ID, URL, or draft location) or the role of client_id. An agent could invoke it, but could not describe the result or scope it to a client without guessing.

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 coverage is 67%: keyword and word_count are documented in the schema, leaving client_id with no explanation anywhere. The description reinforces only the keyword input and adds nothing about client_id ownership or how word_count interacts with the article structure, so baseline 3 applies.

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 names a specific verb and resource ("Writes an SEO article") and adds the scope that it is keyed on a keyword and saved as a draft. It does not, however, distinguish this tool from the closely named sibling seo_content_write, so an agent still has to infer which of the two to call.

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 context is only implied: generating an article implies you first need a keyword and a client, and "Nothing is published" signals the draft-only boundary. No explicit when-to-use vs. when-not guidance or named alternative is given, leaving the seo_content_write overlap unresolved.

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.