Skip to main content
Glama

ADS Beast

seo_brief_generate

Read-only

A content brief for one keyword: headings, meta tags, structure, related terms, length. 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": {
      "keyword": "<keyword>"
    },
    "name": "seo_brief_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
geoNoCountry: SK.
urlNohttps:// page URL.
keywordYesTarget search query.
languageNoen, sk
client_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: the AI-request cost and the possibility of an asynchronous job_id requiring a follow-up call. It doesn't say whether the brief is persisted or how long jobs take.

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?

Extremely tight and front-loaded — deliverable first, then cost, then async follow-up. The telegraphic fragment style is slightly choppy but every clause carries information; nothing is 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 5-parameter tool with no output schema, the description covers the return shape, cost, and async behavior, which is the important part. It leaves the optional url and client_id paths unexplained, so an agent doesn't know whether supplying a URL changes the brief's basis.

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 80%, so the schema already documents geo, url, keyword, and language; the description only reinforces the 'one keyword' requirement. It adds no meaning for client_id, the sole undocumented parameter, so baseline 3 is appropriate.

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 concrete deliverable — a content brief for one keyword — and enumerates its components (headings, meta tags, structure, related terms, length), which separates it from sibling generators like seo_article_generate or seo_schema_generate. It never explicitly names a sibling as the alternative, so it stops 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 Guidelines3/5

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

Implies usage context through 'one keyword' scoping and gives a useful follow-up rule ('May return a job_id (get_job_result)'), plus a cost signal ('1 AI request'). However, it never says when to pick this over seo_content_write or seo_article_generate, nor any prerequisites for the url/client_id path.

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.