Context — ctxt.io

Create a ctxt.io share link

create_context

Share text, markdown, code, or HTML as an auto-expiring ctxt.io link. For visual output (styled reports, tables, charts, diagrams) prefer format=html with self-contained HTML: inline CSS and inline SVG render fully; is stripped server-side and JavaScript never runs, so keep it static. Free expiries: 5m, 30m, 1h (default), 8h, 1d — these return the share URL immediately. ttl=30d and the Pro options (name, password) cost $1 one-time: the link is created in a pending state and the result includes a payment_url a human can open in a browser to complete checkout (platforms enrolled for agentic payments receive an acp block instead and can pay programmatically); until payment the link lives 1 day without Pro features. Anyone with the link can read it. The returned delete_token authorizes deletion via delete_context — keep it private.

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": {
      "content": "<content>"
    },
    "name": "create_context"
  }
}

Input Schema

Name	Required	Description	Default
`ttl`	No	How long the link stays readable. 5m–1d are free; 30d costs $1.	1h
`lang`	No	With format=code: the language to highlight (e.g. python, javascript, diff). Omit to auto-detect.
`name`	No	Pro, ttl=30d only: human-readable name appended to the URL as a slug.
`format`	No	How to render the content: text (verbatim), markdown (rendered rich), code (syntax highlighted), or html (sanitized and rendered — best for visual output; inline CSS/SVG work, scripts are stripped).	text
`content`	Yes	The content to share (max 4MB).
`password`	No	Pro, ttl=30d only: password required to read the link. Access control, not encryption — content is plaintext at rest.

Output Schema

Name	Required	Description
`acp`	No	Present when this deployment accepts Agentic Commerce Protocol payments: checkout_endpoint + item_id let an enrolled agent platform complete the $1 purchase without a browser.
`url`	Yes
`x402`	No	Present when this deployment accepts x402 payments: any agent with an x402 wallet can pay the $1 via the upgrade_context tool — no enrollment.
`html_url`	Yes
`json_url`	Yes
`text_url`	Yes
`expires_at`	Yes
`manage_url`	Yes	The share URL with ?t=<delete_token> already appended: opening it in a browser unlocks delete/upgrade for this link — share it only with the link's owner.
`payment_url`	No
`delete_token`	Yes	Short creator token: authorizes delete_context, and appended to the share URL as ?t=<delete_token> it unlocks delete/upgrade in a browser — keep it private.
`markdown_url`	Yes
`pending_payment`	Yes
`paid_ttl_seconds`	No
`current_ttl_seconds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 2, 2026

addedOutput schema / properties / html_url
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "url",
-  "markdown_url",
-  "text_url",
-  "json_url",
-  "expires_at",
-  "current_ttl_seconds",
-  "pending_payment",
-  "delete_token",
-  "manage_url"
-]New value: +[
+  "url",
+  "markdown_url",
+  "text_url",
+  "json_url",
+  "html_url",
+  "expires_at",
+  "current_ttl_seconds",
+  "pending_payment",
+  "delete_token",
+  "manage_url"
+]

Changed2 schema fields changedAug 28, 2026

addedOutput schema / properties / delete_token / description

Added value: +"Short creator token: authorizes delete_context, and appended to the share URL as ?t=<delete_token> it unlocks delete/upgrade in a browser — keep it private."

changedOutput schema / properties / manage_url / description

Previous value: -"Browser page where a human holding this link's delete_token can delete or upgrade it later — share it only with the link's owner."New value: +"The share URL with ?t=<delete_token> already appended: opening it in a browser unlocks delete/upgrade for this link — share it only with the link's owner."

First observedAug 17, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Discloses behavior well beyond annotations: server-side script stripping, immediate vs. pending link creation, payment_url/acp payment options, 1-day fallback lifespan until payment, public readability, and the delete_token's authorization intent. This is consistent with readOnlyHint=false and destructiveHint=false; 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.

Conciseness5/5

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

The description is dense but every sentence earns its place: purpose first, then format guidance, then expiration/payment behavior, then security. It is front-loaded with the most actionable information and avoids repetition of schema examples.

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?

It covers all non-obvious operational behaviors an agent must know: payment states, pending links, default TTL, public readability, and deletion authorization. Since an output schema exists, return-value documentation is already handled. Complete for a 6-parameter tool with this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even with 100% schema coverage, the description adds meaningful semantics: format=html rendering details (inline CSS/SVG, script stripping), ttl pricing tiers, Pro-only name/password constraints, password as access control not encryption, and the pending payment state for paid options.

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 description opens with 'Share text, markdown, code, or HTML as an auto-expiring ctxt.io link,' which states a specific verb and resource. The title 'Create a ctxt.io share link' reinforces the action, and the content types are enumerated. This clearly distinguishes create_context from its read/delete siblings.

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?

The description gives strong contextual guidance: 'For visual output... prefer format=html', explains free vs. paid ttl options, and details the pending-state/payment flow. It does not explicitly contrast with sibling tools, but the read/delete roles are inherent and it references delete_context when explaining the delete_token.

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

All Context — ctxt.io tools Inspect

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.