Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get a tracked link

analytics_getLink
Read-onlyIdempotent

Returns the specified tracked link, including its destination URL and slug.

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": {
      "siteId": "<siteId>",
      "linkId": "<linkId>"
    },
    "name": "analytics_getLink"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkIdYesID of the tracked link.
siteIdYesThe Sextant site ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds a modest amount of behavioral context by disclosing the returned fields (destination URL and slug), but says nothing about behavior when the link is missing or about permissions.

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?

A single sentence with zero filler, front-loading the action and the returned content. Nothing is repeated from the schema or annotations.

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?

The tool is simple (two required params, full schema coverage, rich annotations), so the bar is low, but with no output schema the description is the only source of return-value information and it only names two fields. Error behavior for a nonexistent linkId is left unspecified.

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 both parameters (siteId, linkId) are already documented in the schema. The description adds no extra meaning about their format, sourcing, or relationships, so the baseline of 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 gives a specific verb and resource ("Returns the specified tracked link") and adds what the payload contains (destination URL and slug). The singular "specified tracked link" implicitly contrasts with the plural listing sibling analytics_getLinks, though no sibling is named explicitly.

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 is only implied: an agent can infer this is for fetching one link when it already has a linkId, versus listing links. There is no explicit when-to-use, when-not-to-use, or named alternative, and no mention of prerequisites such as needing a valid siteId/linkId pair.

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