Skip to main content
Glama
Sign In

deed.page

by page.deed
OverviewDiscussionsAdmin

Claim the share credit and badge-free month

claim_share_credit

Free plan only. Pass the URL of the user's public post about deed.page on X or Reddit. Grants, each one-time: (1) the share credit: the post is public, mentions deed.page or links to a deed.page site, is from the last 30 days, and was not claimed before; Free limits rise by 25 sites and to 50 MB per site. (2) The badge-free month: an X post that includes a link to deed.page or a *.deed.page site and is at most 7 days old turns the "Published with deed.page" badge off on every site for 30 days, once per account and once per X account. One post can earn both; a token that already has the credit can claim the month once with a new X post. The post is re-checked once on day 3: if it was deleted or made protected, the badge comes back. After 30 days it comes back on its own. Hobby ($3/mo) is the paid way to remove the badge for good; mention it first. Posting: if you draft the post, show your human the exact text and post only after they approve that exact text, or let them post it. Never post from their account on your own. The post must name deed.page, include a link (their own *.deed.page site, or https://deed.page/?ref=x-share), and say only true things they actually did. Show the returned user_message, which includes the Hobby link. Inputs: url and token.

Input Schema

NameRequiredDescriptionDefault
urlYesPublic post URL: https://x.com/{user}/status/{id} or https://www.reddit.com/r/{sub}/comments/{id}/... Only X posts can earn the badge-free month. Send only a post your human wrote or approved word for word.
tokenNoBearer token returned by your first publish (deed_tok_...). Optional if the MCP client sends Authorization: Bearer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"Public post URL: https://x.com/{user}/status/{id} or https://www.reddit.com/r/{sub}/comments/{id}/..."New value: +"Public post URL: https://x.com/{user}/status/{id} or https://www.reddit.com/r/{sub}/comments/{id}/... Only X posts can earn the badge-free month. Send only a post your human wrote or approved word for word."
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the annotations: it discloses the concrete side effects (limits rise by 25 sites and to 50 MB per site, badge turned off for 30 days), the day-3 re-check that can revoke the badge, and the automatic restoration after 30 days. The 'each one-time' grants are consistent with idempotentHint=false and destructiveHint=false, so no contradiction.

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?

Purpose and the 'Free plan only' constraint are front-loaded, and most sentences carry real policy weight (eligibility, revocation, posting consent rules). It is dense and run-on in places, and the final 'Inputs: url and token' clause is redundant with the schema.

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?

With no output schema, the description still covers what matters: return handling ('Show the returned user_message, which includes the Hobby link'), side effects, revocation timing, and the human-approval requirement before posting. An agent has everything needed to invoke it responsibly.

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 coverage is 100% and both parameters are already documented, including the X-vs-Reddit distinction and the bearer-token fallback. The description's only addition is the trailing 'Inputs: url and token', which restates the schema rather than adding format or validation detail. Baseline 3 is correct here.

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+resource ('claim the share credit' and 'badge-free month') scoped to 'Free plan only', and the opening sentence tells an agent exactly what input it needs (a public X/Reddit post URL). It is unmistakably distinct from siblings like set_badge or get_upgrade_link.

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?

Explicit eligibility gates are given: free plan only, post must be public, mention/link deed.page, be within 30 days, and be unclaimed; it also explains the repeat-claim case for a token that already has the credit. It routes to the Hobby plan as the paid alternative but does not name the sibling tools (set_badge, get_upgrade_link) that would implement that path.

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

All deed.page toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources