Skip to main content
Glama

classroom_copy_post

Copies an assignment or material from one Google Classroom course to up to 10 other courses as editable drafts, keeping titles, instructions, points, attachments, and matching topics.

Instructions

Copy an assignment or a material to other courses (for example the same unit for several groups). Copies are always created as DRAFT with the same title, instructions, points and attachments; the topic is matched by name and created if missing. Copies made here stay editable by this app.

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": {
      "sourceCourseId": "<sourceCourseId>",
      "id": "<id>",
      "kind": "<kind>",
      "targetCourseIds": "<targetCourseIds>"
    },
    "name": "classroom_copy_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID of the assignment or material to copy
kindYes
dueDateNoYYYY-MM-DD for the copies (assignments). Default: the original due date if it is still in the future, otherwise none.
dueTimeNoHH:MM in local time; requires dueDate
keepTopicNoPlace each copy under a topic with the same name
sourceCourseIdYes
targetCourseIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only flag readOnlyHint=false and openWorldHint=true, so the description carries the real burden and does so well: the DRAFT status of the copies, the fields that are carried over, the fact that the topic is matched by name and created if missing, and editability within this app. It omits failure behavior, such as partial copies, permission requirements, or invalid target courses.

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 dense sentences, with the action front-loaded and the behavioral caveats grouped afterward; every clause adds information (DRAFT state, field inheritance, topic creation) with no padding.

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 mutation tool with no output schema and 7 parameters, the description covers the essentials, such as the resulting post state, field inheritance and topic side effect. Remaining gaps, which are the success/failure return shape and per-course permission requirements, are relatively minor given the openWorldHint mutation.

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 57%, so the schema documents id, dueDate, dueTime and keepTopic while leaving kind, sourceCourseId and targetCourseIds to inference. The description implies the kind value ("assignment or material") and the multi-course target ("other courses"), but says nothing about the target course ID format, the max of 10 targets, or that due dates default from the original, so the baseline 3 is right.

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 ("Copy") plus the exact resources ("an assignment or a material") and the scope ("to other courses"), which cleanly separates it from the create_* siblings. The parenthetical example of the same unit across several groups makes the intent unmistakable.

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 cross-course duplication scenario with the "same unit for several groups" example makes it clear when to use the tool. It stops short of saying when not to use it (for example, preferring create_assignment for a brand-new post) or naming alternatives, so this is a clear context rather than full routing guidance.

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