BriefMe

Add a block to an agenda

add_block

Adds one block to an existing agenda: at the end, above a final wrap-up, or directly after after_block_id.

Adds only — it does not reorder or change any existing block. Returns the full updated agenda, so no get_agenda call is needed afterwards.

Input Schema

TableJSON Schema

Name	Required	Description
`title`	Yes	Short, active, scannable on a countdown screen.
`block_type`	Yes	Internal classification for aggregate analysis, inferred from the content; shown on no BriefMe page.
`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.
`description`	No	Optional one-line note, only when the title is ambiguous.
`share_token`	No	Agenda id (from create_agenda or list_agendas). Required with a linked account, optional beside edit_token.
`after_block_id`	No	Insert directly after this block id. Omit to add at the end.
`idempotency_key`	No	Optional. Re-issuing a call with the same key and the same arguments returns the original result instead of repeating the change — send the same key when re-issuing a request whose response was lost. A fresh UUID per call works well; only a retry repeats one.
`duration_seconds`	Yes	How long this block runs, in seconds.

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.

Changed7 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 / idempotency_key

Added value: +{
+  "description": "Optional. Re-issuing a call with the same key and the same arguments returns the original result instead of repeating the change — send the same key when re-issuing a request whose response was lost. A fresh UUID per call works well; only a retry repeats one.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}

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",
-  "duration_seconds",
-  "block_type"
-]New value: +[
+  "title",
+  "duration_seconds",
+  "block_type"
+]

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

changedInput schema / properties / after_block_id / description

Previous value: -"Insert directly after this block id. Omit to append to the end."New value: +"Insert directly after this block id. Omit to add at the end."

Changed2 schema fields changedSep 11, 2026

changedInput schema / properties / block_type / description

Previous value: -"Internal classification for analysis — infer it from the content; never mention it to the user."New value: +"Internal classification for aggregate analysis, inferred from the content; shown on no BriefMe page."

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

Behavior4/5

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

Annotations already cover readOnly=false, destructive=false, and idempotent=false. The description adds real value: it is purely additive, leaves existing blocks untouched, and returns the full updated agenda so a follow-up get_agenda is unnecessary. It does not reconcile the idempotency_key parameter with idempotentHint=false.

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?

Two tight paragraphs, front-loaded with the action and the placement semantics before the behavioral note. Slight polish issue: the duplicated word in 'after after_block_id'.

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?

An output schema exists, so return values need not be detailed, and the description still usefully notes the full agenda is returned. Token/auth details live in the schema. Complete for an additive write tool, with only the idempotency nuance unaddressed.

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 description coverage is 100%, so baseline is 3, but the description adds positional semantics for after_block_id ('insert directly after', omit for end) and clarifies the placement model beyond what the schema states. Other parameters (tokens, duration) are left to 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 ('Adds one block to an existing agenda') and enumerates the three insertion positions. This clearly separates it from siblings like update_block, reorder_blocks, and remove_block.

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 placement options (end, above a wrap-up, or after after_block_id) and explicitly notes it does not reorder or modify existing blocks, which implicitly steers agents away from reorder_blocks/update_block. It stops short of naming those alternatives directly.

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?