Skip to main content
Glama

List a client's connect links

clipember_list_client_connect_links
Read-onlyIdempotent

List the connect links of one client, newest first: status (active, used, expired, revoked), which networks the client already connected and with which accounts, how often the page was opened, and the client's last attempt. The link URL itself is never shown again.

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": {
      "clientId": "<clientId>"
    },
    "name": "clipember_list_client_connect_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuinely new behavior: results are ordered newest first, status can be active/used/expired/revoked, and critically the link URL is never retrievable after creation — a fact an agent could not learn from the schema and might otherwise assume.

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?

One front-loaded sentence: verb and resource first, then a compact colon-delimited enumeration of returned fields, then the one caveat that matters. No filler or redundant restatement of the tool name.

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?

There is no output schema, so the description must describe return contents, and it does so field by field, including status vocabulary. The only gap is pagination or result-size behavior for a list that could grow across many links, which is not addressed.

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?

With a single required clientId parameter and 0% schema description coverage, the description supplies only 'of one client', which confirms the parameter scopes the listing but adds no format, lookup, or error semantics. The schema's uuid format carries the rest, so this is adequate but thin.

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?

States a specific verb and resource ('List the connect links of one client') and immediately enumerates what each entry contains (status values, connected networks/accounts, open counts, last attempt). This is clearly distinguishable from sibling mutations like create_client_connect_link and revoke_client_connect_link.

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 implied by the scoping to a single client and the read-only listing verb, but there is no explicit statement of when to use this versus revoking or creating a link, nor any prerequisite about client existence or permissions. An agent can infer the context, but nothing is spelled out.

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