Skip to main content
Glama

List the website’s share links

websiteShareLinks_list
Read-onlyIdempotent

Lists the website’s share links: paths such as /menu.pdf that open one of its images or files. Give people each url, not the file’s CDN delivery URL.

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": {
      "websiteId": "<websiteId>"
    },
    "name": "websiteShareLinks_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
websiteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the description doesn't need to restate safety. It instead adds behavior the structured fields don't carry: list entries are site-relative paths, and a `url` field exists that is distinct from the file's CDN delivery URL — a real usage hazard the agent would otherwise trip over. It stops short of describing ordering or pagination.

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 tight sentences, zero filler, with the core definition front-loaded and the URL caveat trailing as a caution. The colon construction that introduces the path example is slightly clunky but costs nothing in comprehension.

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 full annotation coverage, this covers purpose, what an item looks like, and which URL to surface. The absence of an output schema means a little more return-shape detail (other fields per link, ordering, empty-list behavior) would help, but nothing an agent needs to call it correctly 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?

There is a single required `websiteId` parameter with 0% schema description coverage, and the description never mentions it. The name makes the intent self-evident, so this is not damaging, but the description adds no meaning beyond the schema for the one parameter it has.

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 opens with a specific verb and resource ("Lists the website's share links") and then qualifies what a share link actually is — a path like `/menu.pdf` pointing at one of the site's images or files. That makes the purpose concrete enough to distinguish it from the sibling mutators websiteShareLinks_set and websiteShareLinks_remove without opening their schemas.

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 only implied: an agent can infer this is the retrieval path when it needs a site's share links, and the closing clause gives practical guidance on which `url` to hand to people. There is no explicit when-to-use/when-not statement nor a named alternative, so guidance is present but thin.

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