Skip to main content
Glama

Get Share Links

get_share_links
Read-onlyIdempotent

Get the shareable links for a live event — public URL, vanity short link, and every trackable custom link with its source and click count. Every link returned still resolves, including vanity URLs the host has replaced — use it to answer "does the link I already sent still work?". Requires event_id; you must be a host. Read-only.

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": {
      "event_id": "<event_id>"
    },
    "name": "get_share_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered before the description is read. The description still adds real value beyond them: the host-level auth requirement, and the non-obvious guarantee that previously replaced vanity URLs continue to resolve. It does not cover rate limits or result size/pagination, and "Read-only." merely restates the annotation.

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?

Three sentences, front-loaded with the return contents, then the distinguishing use case, then the constraint. Only "Read-only." fails to earn its place, and that is a minor redundancy rather than bloat.

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?

With no output schema, the description correctly carries the burden of describing the return value by naming each link type and its metadata. Combined with the auth prerequisite and the required parameter, an agent has what it needs to call this tool correctly, though the unresolved event_id format leaves a small gap.

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% for the single event_id property, so the description is the only source of parameter meaning and it supplies just the requirement, not the form. It does not say what an event_id looks like, where the agent obtains one, or that it is constrained to 64 characters, which the schema enforces silently.

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 uses a specific verb and resource ("Get the shareable links for a live event") and then enumerates what that resource contains: public URL, vanity short link, and trackable custom links with source and click count. That level of specificity lets an agent distinguish it from neighboring read tools such as get_event_revenue or get_invitation_status without opening any schema.

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 gives a concrete use case — answering "does the link I already sent still work?" — which tells the agent which question this tool exists to answer, and it states the access prerequisite ("you must be a host"). It stops short of naming an alternative tool or stating when not to use it, so it is clear context without explicit routing.

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.