Skip to main content
Glama

MentionedOn Visibility and Website Fixes

Build an AI Visibility Action Plan

build_visibility_action_plan
Read-only

Use after analyze_discovery_readiness, or with findings you already have: turns them into a short ordered list of fixes for one goal and effort budget, with the reason and a check for each. Free; it does not edit a website, contact anyone, store data or promise rankings or mentions.

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": {
      "businessName": "<businessName>",
      "goal": "<goal>",
      "effortBudget": "<effortBudget>",
      "findings": "<findings>"
    },
    "name": "build_visibility_action_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYesThe outcome used to break ties in the deterministic priority rubric.
findingsYesCaller-supplied findings. Present findings are acknowledged but do not create actions.
businessNameYes
effortBudgetYesControls how many actions are returned and how they are phased.

Output Schema

NameRequiredDescriptionDefault
goalYes
scopeYes
actionsYes
goalLabelYes
limitationsYes
businessNameYes
effortBudgetYes
omittedActionCountYes
excludedPresentSignalsYes

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, destructiveHint=false and openWorldHint=false, but the description still adds material context beyond them: it is free, it edits nothing, contacts no one, stores no data, and promises no rankings or mentions. That last clause is important expectation-setting for an agent that might otherwise over-report the plan as an outcome guarantee.

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?

Two sentences, front-loaded with the trigger condition, and the negative scope ("does not edit a website, contact anyone, store data…") is compressed into one clause instead of a list of caveats. No sentence is redundant with the title or the schema.

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 an output schema present, the description need not explain return values, and annotations cover the safety profile; what remains is the sequencing, cost, and side-effect disclosure, all of which are present. The only shortfall is that businessName and the practical effect of the effort budget on plan length are left entirely to the schema.

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 75%, so the schema already documents goal, effortBudget, findings status and evidence in detail. The description only echoes "one goal and effort budget" without explaining, for example, what the effort-budget tiers yield or why businessName is required; it adds meaning mainly about the output shape rather than about parameter semantics.

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 transformation ("turns them into a short ordered list of fixes") plus the two scoping inputs ("one goal and effort budget") and what each item contains ("the reason and a check for each"). An agent can distinguish it from analyze_discovery_readiness (which produces the findings) and from draft_website_fixes (explicitly ruled out: "it does not edit a website").

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?

"Use after analyze_discovery_readiness, or with findings you already have" gives explicit sequencing and an alternate entry condition, which is unusually clear guidance. It stops short of saying when not to use it or which sibling to prefer if the caller has no findings at all, so it is clear context without exclusions.

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