Skip to main content
Glama
Sign In
AgentSEO MCP Server

AgentSEO MCP Server

by AgentSEO-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

AgentSEO Rank Track

agentseo_rank_track
Destructive

Queue a rank tracking check for a URL and keyword to monitor search rankings by location, with an optional bounded wait for results.

Instructions

Queue a rank tracking check for a URL and keyword. Uses AgentSEO credits; repeating the call can create new charged work.

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>",
      "url": "<url>"
    },
    "name": "agentseo_rank_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute web page URL to analyze; use an http:// or https:// URL. Type: String. Format: absolute URL. Required.
syncNoRequest a bounded wait for completion when true. The API can still return a pending job; retain its job ID and poll agentseo_job_status instead of repeating this charged call. False returns a queued job without waiting. Type: Boolean. Default: true.
keywordYesSearch keyword or phrase to analyze for this workflow. Type: String. Required.
locationNoSupported geographic search-market name, for example United States; this is not a coordinate pair. Type: String. Default: "United States".United States

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.5
    • changedInput schema / properties / keyword / description
      Previous value: -"Keyword to track"New value: +"Search keyword or phrase to analyze for this workflow. Type: String. Required."
    • addedInput schema / properties / location / description
      Added value: +"Supported geographic search-market name, for example United States; this is not a coordinate pair. Type: String. Default: \"United States\"."
    • addedInput schema / properties / sync / description
      Added value: +"Request a bounded wait for completion when true. The API can still return a pending job; retain its job ID and poll agentseo_job_status instead of repeating this charged call. False returns a queued job without waiting. Type: Boolean. Default: true."
    • changedInput schema / properties / url / description
      Previous value: -"URL to track"New value: +"Absolute web page URL to analyze; use an http:// or https:// URL. Type: String. Format: absolute URL. Required."
  2. First observedv0.1.4

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the non-idempotent mutation profile is covered structurally. The description adds real context beyond that: the operation consumes AgentSEO credits and repeat invocations create new charged work, which is the key cost consequence an agent needs. It stops short of describing what the queued job returns, but the schema's sync parameter covers the polling path.

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, zero filler, with the core action front-loaded. The cost warning, the single most decision-relevant fact, follows immediately and nothing is repeated.

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 charged async-job tool without an output schema, the description covers the two things that matter: what gets queued and that it costs credits and is not idempotent. It leaves the post-call job lifecycle (retain job ID, poll agentseo_job_status) to the schema, which is acceptable since that text is present there.

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 100%, so every parameter including sync, location, url, and keyword is already documented at the field level. The description names url and keyword but adds no syntax, format, or market-scoping detail beyond the schema. Baseline 3 applies when the schema carries the semantic load.

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 specific verb and resource: 'Queue a rank tracking check for a URL and keyword', which tells an agent exactly what the call initiates. It is distinguishable from most siblings, though the nearest analogue (agentseo_local_visibility_track) is never named or contrasted.

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?

The second sentence implies caution about repeat calls ('repeating the call can create new charged work'), which is useful usage guidance, but no explicit when-to-use/when-not-to-use or alternative tool is named. The more actionable routing advice (poll agentseo_job_status instead of re-calling) lives only in the schema, not the description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools