Skip to main content
Glama

Get My Activity Stream

get_my_activity_stream
Read-only

The authenticated student's cross-course activity stream: new discussion posts, announcements, conversation messages, graded submissions, peer-review requests and conference invitations from every course at once, newest first.

Instructions

The authenticated student's cross-course activity stream: new discussion posts, announcements, conversation messages, graded submissions, peer-review requests and conference invitations from every course at once, newest first. Four caveats, none of them visible in the response: (1) RECENT ACTIVITY ONLY — typically the last ~4 weeks; the retention window is a per-Canvas-instance setting and cannot be read through the API, so "nothing found" is not evidence that nothing happened. (2) Each item's message was truncated to 4096 characters when Canvas stored it, with no marker — follow the item's html_url object with get_discussion or get_conversation for the full text. (3) At most 3 root_discussion_entries per discussion item and 3 latest_messages per conversation item. (4) Exactly one of course_id / group_id is present on each item and the other key is ABSENT, not null — join on course_id, and read context_type to tell which you have.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_itemsNoMaximum items to return (default 100). When the limit is reached, `truncated` is true and `truncation_note` explains how to narrow the query.
only_active_coursesNoOnly return activity in courses the student is actively participating in. Omit to include all courses, including concluded ones.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.18.15

TDQS

A4.5/5.0
Behavior5/5

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

With readOnlyHint/openWorldHint already covering safety, the description adds four non-obvious behaviors beyond annotations: limited retention window with misleading empty results, silent 4096-character truncation, capped nested arrays, and exactly-one context key present (absent vs null), plus follow-up tools for full text.

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?

Front-loads the resource and scope, then presents caveats as a compact numbered list. Despite its length, every sentence carries operational information for a tool with no output schema.

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

Completeness5/5

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

No output schema exists, so the description must carry return-shape details; it does via item types, truncation behavior, nested-array caps, and context_type/course_id/group_id handling, leaving no critical gap for correct invocation.

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 100% and both parameters (max_items, only_active_courses) are fully documented in the schema. The description adds no additional syntax or default semantics, so the baseline 3 is appropriate.

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 resource ('authenticated student's cross-course activity stream'), enumerates item types, ordering ('newest first'), and scope ('from every course at once'), which clearly separates it from course-specific and summary siblings.

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?

Gives clear context for when the feed is appropriate (cross-course, authenticated student) and routes the agent to get_discussion/get_conversation for full text. However, it never explicitly compares against siblings like get_course_activity_stream or get_my_activity_stream_summary, nor states when not to use it.

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

Deploy Server

Other Tools