Skip to main content
Glama
Sign In

upTake

by me.uptake
OverviewDiscussionsAdmin

Create a tracked link

uptake_create_link

Creates a tracked link that tells upTake which visits, signups and payments came from where it is shared.

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": {
      "destination": "<destination>",
      "network": "<network>"
    },
    "name": "uptake_create_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeNoOptional detail of the place: a subreddit (r/SaaS), a newsletter issue (#12), a campaign name.
networkYesWhere the link will be shared: x, linkedin, reddit, newsletter, producthunt, hackernews, youtube…
projectNoWhich project: its id or site (example.com) from uptake_projects. Optional when the maker has a single project.
destinationYesPage to link to. A page of the maker's site gets a direct link; any other address a short /r/ link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world write. The description adds genuinely useful behavioral context — that the link attributes visits, signups and payments — but does not say whether repeat calls create duplicate links, whether a link is reused per network/place pair, or that the caller receives the link back.

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?

A single front-loaded sentence with no filler; the purpose and the value proposition arrive together.

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?

For a 4-parameter mutation with no output schema, the definition leaves out what the tool returns (the tracked URL?) and any prerequisites or duplicate behavior. The rich schema compensates for parameter gaps but not for the missing return/behavior story.

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 100%, so the schema already explains network, destination, place and project semantics (including the direct-link vs /r/ short-link distinction). The description adds only the loose phrase 'where it is shared', which does not extend meaning beyond the schema.

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?

States a specific verb and resource (creates a tracked link) and adds the reason it exists — visit/signup/payment attribution. It is not confused with any sibling, though it never explicitly contrasts with them.

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?

No when-to-use or when-not-to-use guidance, and no mention of the alternative of posting without a tracked link or of the need to resolve a project first (which the schema references via uptake_projects but the description does not). Usage is only implied by the word 'tracked'.

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

All upTake toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources