Skip to main content
Glama

Plunder & Riffle Meme Engine

The owner's offer links

list_my_offers
Read-only

The key owner's own links. pages = our page for each partner (/whop, /polyshares, /amelia…) with their ref on it: share pages[].url; its button is their own link when button is "yours", and it carries 30-day views and clicks. offers = the raw affiliate/referral links they saved; use only these, exactly as written. missing = not saved: ask them to add it on /hub. Free.

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_my_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, but with no output schema the description carries the return-shape burden and does so: it delineates `pages[].url`, `button` == "yours", 30-day views/clicks, `offers` as verbatim saved links, and `missing` as unsaved. It also flags that the call is "Free." What it omits is anything about ordering, scope of partners, or empty-state behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Backticked field names give useful structure and most sentences are information-dense, but the prose is compressed to the point of ambiguity ("The key owner's own links", "our page for each partner", the dangling "Free."). The front-load is a noun phrase instead of the action.

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 zero-parameter, read-only tool with no output schema, the description supplies the three top-level return groups and their meanings, which is the main thing an agent needs. Gaps remain around ordering, what `pages` contains beyond examples, and what an empty `missing` or `offers` implies.

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?

The tool takes zero parameters, so the baseline of 4 applies; there is no parameter meaning left for the description to add or omit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening "The key owner's own links" is a noun phrase rather than a verb-plus-resource statement, so the agent must infer from the name and the field breakdown that this retrieves the owner's offer/referral links. The three named groups (pages, offers, missing) do reveal the resource being returned, but the phrasing is jargon-heavy and never states plainly 'returns your saved offer links'.

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?

Guidance is embedded in output instructions rather than stated as when-to-call: use `offers` "only these, exactly as written" and route unsaved items via /hub. There is no statement of when this tool should be chosen versus alternatives or any precondition, leaving usage only implied.

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