Shager

Tracked links and their clicks

list_links

Read-onlyIdempotent

The workspace's tracked short links, newest first (up to 200): each with its short_url, the original URL, its UTM tags, its clicks, when it was made, and the post and account it belongs to (null for links made by hand or with create_link; auto-reply links carry utm_medium auto-reply). Also the totals for the workspace (clicks and unique visitors, bots left out) and clicks by utm_source (unlabeled = links without a source of their own). For clicks per post, account and network in a period, use get_analytics.

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "list_links"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`workspace_id`	Yes	Workspace id from list_workspaces

Output Schema

Name	Required	Description	Default
`items`	Yes
`next_cursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description focuses on output semantics: returned link fields, null post/account for manual or create_link links, auto-reply utm_medium handling, and totals with bots excluded. This adds substantial context beyond annotations, though it does not discuss pagination beyond the 200 cap.

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?

The description front-loads the resource and scope, then details return contents and alternatives. It is information-dense and long but avoids wasted filler; the single-sentence format is slightly harder to scan than structured bullets.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although an output schema exists, the description still gives useful return-value semantics such as totals excluding bots and unlabeled utm_source meaning links without their own source. For a two-parameter read-only list tool, nothing essential is missing.

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 50%: workspace_id is documented in the schema, but limit is undocumented. The description's phrase 'up to 200' and 'newest first' partially conveys the limit behavior, but it does not explain the limit parameter explicitly or its minimum/maximum range.

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?

The description states a specific resource (workspace's tracked short links) and scope (newest first, up to 200), then enumerates the returned fields. It also distinguishes itself from get_analytics for period-based breakdowns, so an agent can identify the tool without opening schemas.

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?

It explicitly routes the agent to get_analytics for clicks per post, account, and network in a period. The main use case is clear, though there is no explicit statement of when not to use this tool beyond that single alternative.

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

All Shager tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?