Shager

List client connect links

list_connect_links

Read-onlyIdempotent

The workspace's connect links that still work (not revoked, not expired): who each is for (label), its url to send again, when it expires (14 days after it was made), when it was last used and how many accounts were connected through it. revoke_connect_link stops one at once. (Not available in an unclaimed sandbox.)

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_connect_links"
  }
}

Input Schema

Name	Required	Description	Default
`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.1/5.0

Behavior4/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description adds real behavioral context on top: revoked and expired links are excluded, links expire 14 days after creation, and the tool is unavailable in an unclaimed sandbox. It stops short of describing pagination or ordering, which is the remaining gap.

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 dense sentence plus two short asides, with the core scope front-loaded before the field enumeration. The list of returned attributes is useful but slightly verbose given an output schema already exists.

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 one-parameter read tool with annotations and an output schema, the agent has everything needed: scope, filtering rules, expiry semantics, environment limitation, and the related mutation tool. The redundant field enumeration is harmless and the missing pagination/ordering note is minor.

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?

Only one parameter and schema coverage is 100%, with the schema itself noting 'Workspace id from list_workspaces'. The description reinforces workspace scoping ('The workspace's connect links') but adds no format or sourcing detail beyond that. Baseline 3 is appropriate.

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?

Specific verb+resource with scope baked in: 'The workspace's connect links that still work (not revoked, not expired)'. It also enumerates exactly what each item carries (label, url, expiry, last used, account count), so the agent knows what it gets without opening a schema. The 'connect links' phrasing plus the pointer to revoke_connect_link separates it from the generic list_links sibling.

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?

Usage context is clear: for reviewing live connect links, with revoke_connect_link named as the follow-up action for stopping one. It also flags the environment restriction '(Not available in an unclaimed sandbox.)'. It doesn't spell out a when-not condition against list_links, which keeps it just short of a 5.

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?