Skip to main content
Glama
Sign In

PubSpace

by ai.pubspace
OverviewDiscussionsAdmin

Keep a preview with an email link

claim_page

For pages published without an API key (previews): ask PubSpace to email your human one link that keeps every page under a claim token. Callable without an API key. Only call it after the human has told you their email; never invent or guess one. Opening the link shows a Keep button; pressing it, or one bare POST to the link (do that if the human pastes it to you), moves the pages into a free PubSpace space at .pubspace.ai (or into the account they already have, as many pages as its plan holds): the preview links redirect there and stop expiring, even after the 7 days. Pass claim_token from publish_page, or omit it in the session that published the preview. Returns { ok, sent, email, expiresInHours, tell_user }: relay tell_user. The answer is the same whether or not the address already has an account. Once the human clicks, the pages that moved answer preview_already_claimed: ask them for their API key to keep updating those. Pages that did not fit an existing account's plan stay previews; the claim token still updates them, and calling claim_page again keeps them once there is room. When every page has moved, the claim token stops working. Fails with invalid_email, disposable_email_not_allowed, email_opted_out, invalid_claim_token, preview_already_claimed or rate_limited.

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": {
      "email": "<email>"
    },
    "name": "claim_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe human's real email address, as they gave it to you. The claim link goes here.
claim_tokenNoThe claimToken publish_page returned. Optional in the MCP session that published the preview.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (which only say it is not read-only, is open-world, and is not idempotent), the description discloses that an email is sent, the exact return shape, the 7-day expiry behavior, what happens to pages that do not fit a plan, that the claim token stops working once all pages move, and the full error-code list including rate_limited. Nothing contradicts the annotations.

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?

The purpose is front-loaded, but the body is a dense run-on paragraph with nested parentheses and multiple clauses per sentence, which makes it harder to scan than it needs to be. Most content earns its place, but the packaging could be tightened into shorter, separated statements.

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?

For a two-parameter, no-output-schema tool, the description covers the return object, the post-claim state, the partial-claim edge case, and every failure mode. An agent has everything needed to call it correctly and to handle the result.

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%, so both parameters are already documented. The description still adds meaning: the email must be the human's real address and must never be invented, and claim_token is optional specifically within the publishing session. That is useful context beyond the schema, though it does not add format or validation detail.

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?

The opening sentence names a specific verb and resource ('ask PubSpace to email your human one link that keeps every page under a claim token') and scopes it to previews published without an API key. This is clearly distinguishable from publish_page, verify_email, and the other siblings.

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?

It gives explicit preconditions ('Only call it after the human has told you their email; never invent or guess one'), states it is callable without an API key, and explains the claim_token alternative ('pass claim_token from publish_page, or omit it in the session that published the preview'). It also routes follow-up behavior after the human clicks, telling the agent to request an API key.

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

All PubSpace 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