Skip to main content
Glama
Sign In

upTake

by me.uptake
OverviewDiscussionsAdmin

Edit a post

uptake_edit_post

Replaces the text of one network's version of a post with the maker's own edit, like typing in upTake's Write studio. Free: no AI, no quota. Refused for a version already published or scheduled, and when the new text drops the tracked link. To rewrite with AI, use uptake_write_post.

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": {
      "post_id": "<post_id>",
      "network": "<network>",
      "text": "<text>"
    },
    "name": "uptake_edit_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe full new text of that version, as it will be posted. Keep its tracked link.
networkYesWhich version to edit: the network of one of the post's versions (see uptake_get_post).
post_idYesId from uptake_posts or uptake_write_post.
projectNoWhich project: its id or site (example.com) from uptake_projects. Optional when the maker has a single project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-destructive, non-idempotent write, and the description adds real context beyond that: it is free with no AI and no quota, it wholesale replaces existing text, and it fails under two named conditions (published/scheduled version, missing tracked link). It stops short of saying whether the prior text is recoverable, which is the one behavior an agent editing over existing content would still want.

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?

Three short sentences with the action front-loaded, then cost, then failure conditions, then the alternative. Nearly every clause earns its place; only the 'like typing in upTake's Write studio' simile is soft, though it usefully conveys a manual-edit mental model.

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?

Covers the action, cost, refusal conditions, and the sibling alternative, which is ample for a 4-parameter edit tool with full schema coverage and no output schema. The only omission is any hint of what a successful edit returns or whether the previous text can be restored.

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 parameters are already fully documented, including the tracked-link requirement on text and how network identifies a version. The description reinforces the one-network-per-call scope but adds little that the schema does not already state, so this sits at the baseline.

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?

States a specific verb and resource ('Replaces the text of one network's version of a post') with explicit scope: the maker's own edit, not an AI-generated one. It names uptake_write_post as the contrasting sibling, so an agent can distinguish the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete when-to-use framing ('like typing in upTake's Write studio') plus explicit when-not conditions: refused for versions already published or scheduled, and when the new text drops the tracked link. It also routes AI rewriting to uptake_write_post, which is exactly the kind of alternative routing that earns a top score.

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