BriefMe

Remove a block

remove_block

DestructiveIdempotent

Removes one block from an agenda. The remaining blocks keep their ids and their order.

An agenda must keep at least one block, so this fails on the last one. Removing a block shortens the meeting — it does not redistribute that time to the other blocks.

Returns the full updated agenda.

Input Schema

TableJSON Schema

Name	Required	Description
`block_id`	Yes	The id of the block to remove.
`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",
-  "block_id"
-]New value: +[
+  "block_id"
+]

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.5/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, but the description adds substantial non-obvious behavior: remaining blocks keep their ids and order, the operation fails on the last block, and removal does not redistribute meeting time. The failure mode and the semantic effect on the agenda are exactly the kind of context annotations 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.

Conciseness5/5

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

Three short, front-loaded statements with zero filler: the core action first, then the ordering/failure constraint, then the return. Every sentence carries distinct information.

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 destructive single-block mutation with an output schema and fully documented parameters, the description covers the action, the invariants, the failure condition, and the return. Nothing an agent needs to invoke this 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 description coverage is 100%, and the auth token semantics (edit_token authorizing on its own, share_token needed with a linked account) are fully documented in the schema. The description adds no parameter-level detail beyond what the schema already provides, so 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?

States a specific verb and resource ('Removes one block from an agenda') and is immediately distinguishable from siblings like add_block, update_block, and reorder_blocks. An agent can tell exactly what operation is performed without opening the schema.

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 a clear when-not condition ('An agenda must keep at least one block, so this fails on the last one'), which prevents a foreseeable failure. It does not, however, route the agent to alternatives such as update_block or delete_agenda, so guidance is contextual rather than complete.

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?