Skip to main content
Glama

BriefMe

by us.briefme
OverviewDiscussionsAdmin

Regenerate the edit link

rotate_edit_token
Destructive

Replaces an agenda's edit token and edit link with new ones. The previous edit_token and edit_url stop working the moment this returns, for every assistant, browser and bookmark that held them — the remedy when an edit link was shared by mistake.

Returns the full agenda with the new edit_url and, unless the agenda is saved to a linked BriefMe account, the new edit_token. The previous ones cannot be restored. Agendas expire after 7 days and cannot be recovered afterwards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
edit_tokenNoThe latest edit_token (from create_agenda, or rotate_edit_token after a rotation). Authorizes on its own; needed unless the agenda is saved to a linked account.
share_tokenNoAgenda id (from create_agenda or list_agendas). Required with a linked account, optional beside edit_token.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
blocksYesThe blocks in the order they run.
edit_urlYesThe user's new private control page; the previous link is dead.
share_urlYesThe read-only agenda with the live timer; safe to give to attendees.
edit_tokenNoWhat later anonymous calls take. Absent when the agenda is saved to a linked account.
expires_atYesISO 8601. null when the agenda is saved to an account and does not expire.
share_tokenYesThe agenda's public identifier; what every tool takes as share_token.
instructionsYesWhat the user needs from this result.
total_secondsYesSum of every block's duration_seconds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / edit_token / description
      Previous value: -"The current edit_token — the one being replaced."New value: +"The latest edit_token (from create_agenda, or rotate_edit_token after a rotation). Authorizes on its own; needed unless the agenda is saved to a linked account."
    • addedInput schema / properties / share_token
      Added value: +{
+  "description": "Agenda id (from create_agenda or list_agendas). Required with a linked account, optional beside edit_token.",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "edit_token"
-]
    • changedOutput schema / properties / blocks / items / properties / block_type / description
      Previous value: -"Internal classification; never mention it to the user."New value: +"Internal classification; appears on no BriefMe page."
    • changedOutput schema / properties / edit_token / description
      Previous value: -"What every later tool call takes from now on; the previous token is dead."New value: +"What later anonymous calls take. Absent when the agenda is saved to a linked account."
    • changedOutput schema / properties / instructions / description
      Previous value: -"Read this first: how to reply to the user."New value: +"What the user needs from this result."
    • addedOutput schema / properties / share_token
      Added value: +{
+  "description": "The agenda's public identifier; what every tool takes as share_token.",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "instructions",
-  "edit_url",
-  "edit_token",
-  "title",
-  "total_seconds",
-  "expires_at",
-  "share_url",
-  "blocks"
-]New value: +[
+  "instructions",
+  "edit_url",
+  "title",
+  "total_seconds",
+  "expires_at",
+  "share_token",
+  "share_url",
+  "blocks"
+]
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the destructiveHint=true annotation, it discloses the precise blast radius (old tokens stop working the moment it returns, affecting all holders), irreversibility (cannot be restored), and a time constraint (7-day agenda expiry). This is exactly the behavioral context annotations alone cannot convey.

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?

Front-loaded with the core action and consequence, then the return shape, then the expiry caveat. Generally tight, though the irreversibility point is stated twice ('cannot be restored' / 'cannot be recovered'), which is mild redundancy.

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?

An output schema exists, so return values need no explanation, and the description still covers scope, irreversible consequence, and expiry. For a destructive rotation tool, nothing an agent needs to call it correctly is missing.

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%, so both parameters are already documented, including the linked-account branching for edit_token. The description largely reinforces this rather than adding syntax or format details beyond the schema, so the baseline 3 applies.

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?

Specific verb+resource: it replaces an agenda's edit token and edit link with new ones, and explicitly frames the scope of the effect (every assistant, browser, bookmark). This is clearly distinguishable from siblings like update_agenda or create_agenda.

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?

Provides a clear when-to-use trigger — 'the remedy when an edit link was shared by mistake' — which is exactly the context an agent needs. It does not enumerate alternatives or exclusions, so it falls short of a full 5.

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

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