Skip to main content
Glama

Geoa — Get found in ChatGPT

Draft Article from Visibility Gap

geoa_draft_from_gap

Create a source-verified article draft from an AI-visibility gap (e.g. a question from geoa_ai_visibility). The draft is generated with the customer's Brand Brain, source-verified by the Gate and scored by the Coach — and lands as a DRAFT in Content Studio; nothing is published automatically. Requires a sign-in to a geoa account; counts against the plan's article quota.

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": {
      "question": "<question>"
    },
    "name": "geoa_draft_from_gap"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoda (default), no, sv or en
questionYesThe question/topic the draft should answer
cited_insteadNoCompetitor domains cited instead (from geoa_ai_visibility)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and idempotentHint=false; the description adds meaning beyond them — output lands as a DRAFT in Content Studio, nothing is auto-published, auth is required, and the call consumes plan quota. That quota/non-idempotency implication is exactly the kind of side-effect context annotations can't convey.

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 dense sentences, front-loaded with the action and followed by safeguards and prerequisites. No filler or restated title.

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 mutation tool with no output schema, the description covers side effects, auth and quota well. It stops short of saying what the caller receives (e.g. draft ID, status or URL), which would help an agent chain follow-up calls.

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 100%, so question, language and cited_instead are fully documented in the schema. The description reinforces where 'question' and 'cited_instead' come from (geoa_ai_visibility) but says nothing about the language parameter, so it adds only marginal value over the schema.

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?

States a specific verb and resource ('Create a source-verified article draft from an AI-visibility gap') and ties the input source to the sibling geoa_ai_visibility. An agent can distinguish this from read-only siblings like geoa_ai_visibility or geoa_ready_articles without opening a schema.

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?

Gives a clear context for use (a gap surfaced by geoa_ai_visibility) and names prerequisites: a geoa sign-in and quota consumption. It does not explicitly name an exclusion or point to a specific alternative when quota runs out, so it falls short of a full when/when-not treatment.

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.

Resources