Skip to main content
Glama
Sign In
google-workspace-mcp-advanced

google-workspace-mcp-advanced

by Skeptomenos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

read_presentation_comments

Access all comments in a Google Presentation for reviewing feedback and tracking discussion threads.

Instructions

Read all comments from a Google Presentation.

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": {
      "user_google_email": "<user_google_email>",
      "presentation_id": "<presentation_id>"
    },
    "name": "read_presentation_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_google_emailYes
presentation_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.10

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description must disclose behaviors, but it only states the basic operation. It does not mention whether replies are included, auth requirements, pagination, or the non-destructive nature of the read action.

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, front-loaded sentence with no unnecessary words. It is maximally concise while still conveying the core purpose.

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 two required parameters, zero schema descriptions, no annotations, and no parameter guidance, the description is inadequate for an agent to confidently invoke the tool. It only identifies the operation and resource, but omits essential contextual details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for the two required parameters (user_google_email, presentation_id). It does not mention or explain either parameter, forcing the agent to rely solely on parameter names.

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?

The description clearly identifies the verb 'Read' and the resource 'comments from a Google Presentation,' which is specific and distinguishes it from sibling comment tools for documents and spreadsheets. It is unambiguous about what the tool does.

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?

The description provides no guidance on when to use this tool versus alternatives such as create_presentation_comment or reply_to_presentation_comment. It lacks any contextual cues about scenario fit or exclusions.

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