Skip to main content
Glama
@elido/mcp-server

@elido/mcp-server

Official
by elidoapp

list_links

Retrieve recent links in a workspace with limit and offset pagination to browse link history page by page.

Instructions

List recent links in the workspace. Use limit/offset for pagination.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not disclose sort order, what "recent" bounds are, default page size, required permissions, or the shape of returned items — all material for a listing tool with zero annotation coverage.

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?

Two short sentences, front-loaded with the purpose before the pagination note, with no filler. The brevity is appropriate, though the word "recent" is left undefined and slightly undermines the efficiency.

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?

This is a simple read tool with two optional parameters and no output schema, so the bar is low and purpose plus pagination is minimally sufficient. Still missing is any statement of ordering or recency scope, which an agent needs to page correctly and interpret results.

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 0%, so the description must compensate; it does partially by framing limit and offset as pagination controls rather than filters. However, it adds nothing about the default of 20, the maximum of 100, or how offset interacts with a changing "recent" window.

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 states a specific verb and resource ("List recent links in the workspace"), so the agent can tell it apart from create_link and generate_qr. It stops short of differentiating from list_workspaces or defining what "recent" means, so it is clear but not maximally specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is "Use limit/offset for pagination," which is parameter advice rather than when-to-use guidance. It never says when to choose this tool over list_workspaces or query_analytics, and gives no preconditions or exclusions.

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