google-classroom-mcp

Overview Schema Source Related Servers Discussions Admin

classroom_create_assignment

Create a Google Classroom assignment or question with attachments, due date, topic, and scheduling options. Publish or save as draft.

Instructions

Create an assignment or question with optional attachments, due date, and topic.

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>",
      "title": "<title>"
    },
    "name": "classroom_create_assignment"
  }
}

Input Schema

Name	Required	Description	Default
`state`	No		DRAFT
`title`	Yes
`dueDate`	No	YYYY-MM-DD in UTC
`dueTime`	No	HH:MM in UTC (defaults to 23:59 if dueDate is set)
`topicId`	No
`courseId`	Yes
`workType`	No		ASSIGNMENT
`maxPoints`	No
`attachments`	No
`description`	No
`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

B3.2/5.0

Behavior3/5

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

Annotations mark readOnlyHint as false, and the description's 'Create' is consistent, adding that this is a mutation that produces a new assignment or question. It does not disclose defaults like DRAFT state or the returned value, but the annotations and schema already carry part of the safety and mutation signal.

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?

The description is a single, well-structured sentence that front-loads the core action ('Create an assignment or question') and then lists optional context. There is no filler or redundancy.

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 11 parameters, low schema description coverage, and no output schema, the description does not cover important decisions such as DRAFT vs PUBLISHED state, scheduledTime, maxPoints, workType, or what the method returns. An agent would need to infer too much from names and enums.

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 27%, and the description merely echoes 'attachments, due date, and topic' without explaining their types, required values, or behavior. It hints at workType through 'question' but leaves state, maxPoints, scheduledTime, dueTime, and attachment structure mostly unexplained.

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 clearly states the verb 'Create' and the resource 'assignment or question', and it names common optional aspects like attachments, due date, and topic. It is distinguishable from classroom_create_topic because the topic is an optional property rather than the primary resource, though it does not explicitly contrast with classroom_patch_assignment.

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

Usage Guidelines3/5

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

The word 'Create' implies this is for new assignments or questions, and sibling names like classroom_patch_assignment and classroom_create_topic hint at alternatives. However, there is no explicit guidance on when to use this instead of patching an existing assignment or when to create a topic first.

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