google_classroom-automation
Original:🇺🇸 English
Translated
Automate Google Classroom tasks via Rube MCP (Composio): course management, assignments, student rosters, and announcements. Always search tools first for current schemas.
2installs
Added on
NPX Install
npx skill4agent add composiohq/awesome-claude-skills google_classroom-automationTags
Translated version includes tags in frontmatterSKILL.md Content
View Translation Comparison →Google Classroom Automation via Rube MCP
Automate Google Classroom operations through Composio's Google Classroom toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/google_classroom
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Google Classroom connection via with toolkit
RUBE_MANAGE_CONNECTIONSgoogle_classroom - Always call first to get current tool schemas
RUBE_SEARCH_TOOLS
Setup
Get Rube MCP: Add as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
https://rube.app/mcp- Verify Rube MCP is available by confirming responds
RUBE_SEARCH_TOOLS - Call with toolkit
RUBE_MANAGE_CONNECTIONSgoogle_classroom - If connection is not ACTIVE, follow the returned auth link to complete setup
- Confirm connection status shows ACTIVE before running any workflows
Tool Discovery
Always discover available tools before executing workflows:
RUBE_SEARCH_TOOLS: queries=[{"use_case": "course management, assignments, student rosters, and announcements", "known_fields": ""}]This returns:
- Available tool slugs for Google Classroom
- Recommended execution plan steps
- Known pitfalls and edge cases
- Input schemas for each tool
Core Workflows
1. Discover Available Google Classroom Tools
RUBE_SEARCH_TOOLS:
queries:
- use_case: "list all available Google Classroom tools and capabilities"Review the returned tools, their descriptions, and input schemas before proceeding.
2. Execute Google Classroom Operations
After discovering tools, execute them via:
RUBE_MULTI_EXECUTE_TOOL:
tools:
- tool_slug: "<discovered_tool_slug>"
arguments: {<schema-compliant arguments>}
memory: {}
sync_response_to_workbench: false3. Multi-Step Workflows
For complex workflows involving multiple Google Classroom operations:
- Search for all relevant tools: with specific use case
RUBE_SEARCH_TOOLS - Execute prerequisite steps first (e.g., fetch before update)
- Pass data between steps using tool responses
- Use for bulk operations or data processing
RUBE_REMOTE_WORKBENCH
Common Patterns
Search Before Action
Always search for existing resources before creating new ones to avoid duplicates.
Pagination
Many list operations support pagination. Check responses for or and continue fetching until exhausted.
next_cursorpage_tokenError Handling
- Check tool responses for errors before proceeding
- If a tool fails, verify the connection is still ACTIVE
- Re-authenticate via if connection expired
RUBE_MANAGE_CONNECTIONS
Batch Operations
For bulk operations, use with in a loop with for parallel execution.
RUBE_REMOTE_WORKBENCHrun_composio_tool()ThreadPoolExecutorKnown Pitfalls
- Always search tools first: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via .
RUBE_SEARCH_TOOLS - Check connection status: Ensure the Google Classroom connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication.
- Respect rate limits: If you receive rate limit errors, reduce request frequency and implement backoff.
- Validate schemas: Always pass strictly schema-compliant arguments. Use to load full input schemas when
RUBE_GET_TOOL_SCHEMASis returned instead ofschemaRef.input_schema
Quick Reference
| Operation | Approach |
|---|---|
| Find tools | |
| Connect | |
| Execute | |
| Bulk ops | |
| Full schema | |
Toolkit docs: composio.dev/toolkits/google_classroom