Skip to main content
Glama

Get app download links

get_app_links
Read-onlyIdempotent

Where to get StoryShort on each platform: the App Store listing for iPhone and iPad, the Mac App Store listing, the web app (any browser, Android included), the Android APK (direct download) and the Android closed beta, plus the URL of a QR code image for the App Store page. Also lists what does not exist yet (a public Google Play listing) so nobody is sent to a link that is not there. For a user who asks how to install, download or open StoryShort. Needs no credentials and no scope. Read-only and free: nothing is created or charged.

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": "get_app_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNoOptional. Return only this platform: ios (iPhone and iPad), macos, web or android. Omit for all of them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the description's marginal job is to add operational context — which it does by stating 'Needs no credentials and no scope' and 'nothing is created or charged,' useful auth/cost expectations an agent won't get from hints alone. It also discloses a negative result ('lists what does not exist yet — a public Google Play listing'), which meaningfully shapes how the agent should present the output. It stops short of describing pagination or error behavior, but that is appropriately minimal for a static lookup.

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?

Front-loaded with the resource scope, followed by the enumeration and then the usage trigger, which is a sensible order. The closing sentence 'Read-only and free: nothing is created or charged' partially restates annotation hints, but it carries cost/auth information that hints do not, so it mostly earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 convey what comes back — and it does, listing every returned link type plus the QR code image URL and the explicit absence of a Google Play listing. Combined with the zero-credential note and single optional filter, an agent has everything needed to call and present results correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the enum is fully documented in the schema, so the baseline is 3. The description adds real semantic value beyond the schema by clarifying the overlapping meanings of the enum values — notably that 'web' covers Android browsers while 'android' refers to the APK and closed beta — which helps the agent map a vague user request to the right filter.

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?

Opens with a specific verb+resource framing ('Where to get StoryShort on each platform') and enumerates exactly which artifacts are returned: App Store, Mac App Store, web app, Android APK, Android closed beta, and a QR code image URL. An agent can immediately distinguish this from sibling tools like get_video or list_pricing, which return unrelated resources.

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?

Gives an explicit trigger condition: 'For a user who asks how to install, download or open StoryShort.' This is clear routing guidance and no sibling tool overlaps that intent. It does not name an alternative or state when-not to call it, but the trigger is narrow enough that this is a minor gap.

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