google-classroom-mcp

Overview Schema Source Related Servers Discussions Admin

classroom_post_announcement

Post announcements to a Google Classroom course stream, with options to save as draft or schedule for later publication.

Instructions

Post an announcement to the course stream.

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": {
      "courseId": "<courseId>",
      "text": "<text>"
    },
    "name": "classroom_post_announcement"
  }
}

Input Schema

Name	Required	Description	Default
`text`	Yes
`state`	No		DRAFT
`courseId`	Yes
`scheduledTime`	No	RFC 3339 timestamp for scheduled publication

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.0.0-beta.1Sep 8, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already indicate a write operation (readOnlyHint=false). The description adds only the 'course stream' context. It does not disclose that the default state is DRAFT, meaning announcements may not be immediately visible in the stream, nor any scheduling or permission side effects.

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?

The single sentence is concise, front-loaded, and contains no filler. However, it is perhaps too terse to be fully helpful, but that is a completeness issue rather than a conciseness defect.

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

Completeness2/5

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

With 4 parameters, an unexpected state default, and no output schema, the description is too minimal. It does not explain the draft/published behavior, scheduling, how the announcement appears in the course stream, or how this operation relates to patching or listing announcements.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25% (scheduledTime alone is described). The tool description fails to compensate by explaining the semantics of text, courseId, or the surprising state default of DRAFT versus PUBLISHED. An agent gets little help interpreting the parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('post'), a resource ('announcement'), and a target location ('course stream'). This clearly distinguishes it from list_announcements and patch_announcement siblings, though it does not explicitly say 'create a new' or contrast with those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus the sibling classroom_patch_announcement or classroom_list_announcements. The verb 'post' implies creation, but the description does not mention exclusions, alternatives, or conditions for selecting this tool.

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