BriefMe

by us.briefme

Overview Discussions Admin

Rename a meeting agenda

update_agenda

DestructiveIdempotent

Renames the agenda. Blocks are untouched — the block tools change those.

Returns the full updated agenda.

Input Schema

TableJSON Schema

Name	Required	Description
`title`	Yes	The new meeting title.
`edit_token`	No	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.
`share_token`	No	Agenda id (from create_agenda or list_agendas). Required with a linked account, optional beside edit_token.

Output Schema

TableJSON Schema

Name	Required	Description
`title`	Yes
`blocks`	Yes	The blocks in the order they run.
`share_url`	Yes	The read-only agenda with the live timer; safe to give to attendees.
`expires_at`	Yes	ISO 8601. null when the agenda is saved to an account and does not expire.
`share_token`	Yes	The agenda's public identifier; what every tool takes as share_token.
`total_seconds`	Yes	Sum of every block's duration_seconds.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 29, 2026

changedInput schema / properties / edit_token / description

Previous value: -"The edit_token returned by create_agenda."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"
+}

changedInput schema / required

Previous value: -[
-  "edit_token",
-  "title"
-]New value: +[
+  "title"
+]

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."

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: -[
-  "title",
-  "total_seconds",
-  "expires_at",
-  "share_url",
-  "blocks"
-]New value: +[
+  "title",
+  "total_seconds",
+  "expires_at",
+  "share_token",
+  "share_url",
+  "blocks"
+]

Changed1 schema field changedSep 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "blocks": {
+      "description": "The blocks in the order they run.",
+      "items": {
+        "properties": {
+          "block_type": {
+            "description": "Internal classification; never mention it to the user.",
+            "enum": [
+              "standup",
+              "discussion",
+              "decision",
+              "q_and_a",
+              "break",
+              "opening",
+              "closing",
+              "other",
+              null
+            ],
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "description": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "duration_seconds": {
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Stable 8-letter id: what update_block, remove_block, reorder_blocks and after_block_id take.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "duration_seconds",
+          "block_type",
+          "description"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "expires_at": {
+      "description": "ISO 8601. null when the agenda is saved to an account and does not expire.",
+      "format": "date-time",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "share_url": {
+      "description": "The read-only agenda with the live timer; safe to give to attendees.",
+      "format": "uri",
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "total_seconds": {
+      "description": "Sum of every block's duration_seconds.",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "title",
+    "total_seconds",
+    "expires_at",
+    "share_url",
+    "blocks"
+  ],
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already supply destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description still adds genuine scope information beyond structured fields — that blocks are untouched and that the full updated agenda is returned — though it does not restate the token/authorization requirement.

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?

Three short sentences with zero filler, front-loading the action and immediately following with the scoping constraint that prevents sibling confusion. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-field rename tool with 100% schema coverage and an output schema, the description covers purpose, sibling disambiguation, and scope. Nothing critical is missing, though it could have noted the destructive nature of overwriting the existing title.

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%, including detailed descriptions for title, edit_token, and share_token, so the schema carries the parameter burden. The description adds no syntax, format, or token guidance beyond what the schema already provides, making the baseline 3 correct.

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 (renames) and resource (agenda) and explicitly disambiguates from the block-editing siblings: 'Blocks are untouched — the block tools change those.' An agent can route between update_agenda and update_block/reorder_blocks purely from this text.

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?

Gives a clear exclusion rule (use the block tools for block changes), which is the primary confusion risk among siblings. It does not address when to use this versus create_agenda or delete_agenda, but those are obvious, so the guidance is adequate without being exhaustive.

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

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

Resources

Need Help?