Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

List my links

analytics_getLinks
Read-onlyIdempotent

Returns a paginated list of the current user's tracked links, with search and sorting options.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
searchNoSearch text used to filter results.
siteIdYesThe Sextant site ID.
orderByNoField to sort the results by.
pageSizeNoNumber of results per page.
maxResultsNoMaximum number of results to include.
sortDescendingNoWhether to sort results in descending order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety and repeatability are covered structurally. The description adds that results are paginated, which is useful beyond the annotations, but it says nothing about default page size, ordering defaults, or whether results are scoped to the caller's account vs. the given siteId.

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?

A single front-loaded sentence that identifies the resource, the pagination behavior, and the supported operations with no filler. It could be slightly sharper by naming the required siteId or the discriminating sibling, but 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?

With 7 parameters, one required siteId, and no output schema, the agent must call this blind about the returned link shape and pagination metadata. The description covers the essentials for a list tool but omits meaningful context such as what a 'tracked link' includes and how results relate to siteId.

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 one of the 7 parameters is already documented in the schema, making 3 the baseline. The description's phrase 'with search and sorting options' loosely frames the search, orderBy, and sortDescending parameters but adds no format or constraint detail beyond what the schema states.

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?

Uses a specific verb and resource ('Returns a paginated list of the current user's tracked links') and names the included capabilities (search, sorting). It is clear what the tool does, but it never distinguishes itself from the singular sibling analytics_getLink or from sites_links, so an agent must infer the boundary itself.

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?

Mentioning 'current user's tracked links' with 'search and sorting options' implies the browsing/filtering use case, which lightly contrasts with a single-link lookup. However, there is no explicit when-to-use or when-not-to-use statement and no named alternative, leaving selection between analytics_getLinks, analytics_getLink, and sites_links to inference.

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