Skip to main content
Glama

canvas_get_account_reports

Retrieve available reports for a specific Canvas account using its ID, enabling efficient management and analysis of course and user data.

Instructions

List available reports for an account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYesID of the account

Implementation Reference

  • src/index.ts:797-807 (registration)
    Tool registration in TOOLS array defining name, description, and input schema
    {
      name: "canvas_get_account_reports",
      description: "List available reports for an account",
      inputSchema: {
        type: "object",
        properties: {
          account_id: { type: "number", description: "ID of the account" }
        },
        required: ["account_id"]
      }
    },
  • Tool handler dispatch in CallToolRequestSchema switch statement, validates args and calls client method
    case "canvas_get_account_reports": {
      const { account_id } = args as { account_id: number };
      if (!account_id) throw new Error("Missing required field: account_id");
      
      const reports = await this.client.getAccountReports(account_id);
      return {
        content: [{ type: "text", text: JSON.stringify(reports, null, 2) }]
      };
    }
  • Core handler implementation in CanvasClient - makes API call to /accounts/{accountId}/reports and returns data
    async getAccountReports(accountId: number): Promise<any[]> {
      const response = await this.client.get(`/accounts/${accountId}/reports`);
      return response.data;
    }
  • Type definition for CanvasAccountReport - output schema for account reports
    export interface CanvasAccountReport {
      id: number;
      report: string;
      file_url?: string;
      attachment?: CanvasFile;
      status: 'created' | 'running' | 'complete' | 'error';
      created_at: string;
      started_at?: string;
      ended_at?: string;
      parameters: Record<string, any>;
      progress: number;
      current_line?: number;
    }
  • Input schema definition for the tool - requires account_id as number
    inputSchema: {
      type: "object",
      properties: {
        account_id: { type: "number", description: "ID of the account" }
      },
      required: ["account_id"]
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'List available reports' but doesn't disclose behavioral traits like whether this is a read-only operation, requires authentication, has rate limits, or what the output format looks like (e.g., list structure, pagination). This leaves significant gaps for a tool with no annotation coverage.

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, efficient sentence with zero waste, front-loading the core action ('List available reports') and resource. It's appropriately sized for a simple tool with one parameter.

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?

Given no annotations, no output schema, and a simple input schema, the description is incomplete. It lacks details on behavioral aspects (e.g., safety, output format) and usage context, making it inadequate for a tool that interacts with account data, even though the parameter is well-documented.

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?

The input schema has 100% description coverage, with the parameter 'account_id' documented as 'ID of the account'. The description adds no additional meaning beyond this, such as format examples or constraints, so it meets the baseline for high schema coverage without compensating value.

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 ('List') and resource ('available reports for an account'), making the purpose specific and understandable. It distinguishes from siblings like 'canvas_list_account_courses' by focusing on reports, but doesn't explicitly differentiate from potential report-related tools (e.g., 'canvas_create_account_report' is a sibling).

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 alternatives. The description lacks context about prerequisites (e.g., needing an account ID), exclusions, or comparisons to other list or get tools in the sibling set, leaving usage ambiguous.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DMontgomery40/mcp-canvas-lms'

If you have feedback or need assistance with the MCP directory API, please join our Discord server