findtime.io MCP Server

Revoke a personal invite link

revoke_invite_link

DestructiveIdempotent

Revokes one personal booking link belonging to the host. linkId identifies an existing link on the host's booking page. Revocation stops future use without cancelling existing requests. Without confirm: true, the operation changes nothing and returns a read-back with status needs_confirmation. confirm: true executes the same operation after the person has confirmed that read-back. Every result has a status listed in the output schema. temporarily_unavailable indicates a temporary service failure.

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": {
      "linkId": "<linkId>"
    },
    "name": "revoke_invite_link"
  }
}

Input Schema

Name	Required	Description
`linkId`	Yes
`confirm`	No	true indicates the person confirmed the read-back returned by the same operation with confirmation omitted.
`_endUserId`	No	Optional opaque per-call end-user attribution token populated by the MCP host, not the LLM. Accepts a non-PII hash or token, excluding raw email addresses, names, or platform user IDs.

Output Schema

Name	Required	Description	Default
`hint`	No
`error`	No
`reason`	No
`status`	Yes
`summary`	No
`readBack`	No
`inviteLink`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations: it discloses that revocation stops future use without cancelling existing requests, describes the read-back/needs_confirmation no-op behavior when confirm is omitted, and explains the status field including the temporarily_unavailable failure signal. This is rich, non-redundant behavioral context for a destructive operation.

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?

Five tight sentences, each carrying distinct information, with the core action and confirmation constraint front-loaded. No filler or repetition of annotation fields.

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?

Anticipates everything an agent needs: confirmation protocol, what revocation does and does not affect, and where statuses are documented via the output schema. Complete for a destructive, idempotent single-resource operation.

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 67% and the description adds meaningful semantics for linkId (must be an existing link on the host's page) and the confirm flow (confirm: true executes after the person confirms the read-back). It doesn't discuss _endUserId, but that parameter is host-populated and already documented in the schema.

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 — 'Revokes one personal booking link belonging to the host' — and scopes it to a single link identified by linkId. This clearly separates it from create_invite_link and the broader booking tools in the sibling list.

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?

Explains that linkId must identify an existing link on the host's booking page and lays out the two-step confirm protocol, which tells the agent exactly when and how to invoke it. It does not explicitly name a sibling alternative or exclusion, so it falls short of a 5.

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

All findtime.io MCP Server tools Inspect

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.