Skip to main content
Glama
Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

Manage Presentation Comment

manage_presentation_comment
Destructive

Create, reply to, resolve, update, or delete comments on Google Slides presentations to manage feedback and review discussions by comment ID.

Instructions

Manage comments on a Google Presentation.

Actions:

  • create: Create a new comment. Requires comment_content. Note: The Drive API cannot anchor comments to arbitrary text; Slides comments are element-scoped via the API.

  • reply: Reply to a comment. Requires comment_id and comment_content.

  • resolve: Resolve a comment. Requires comment_id.

  • update: Edit a comment's text. Requires comment_id and comment_content.

  • delete: Delete a comment. Requires comment_id.

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>",
      "action": "<action>"
    },
    "name": "manage_presentation_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
comment_idNo
comment_contentNo
presentation_idYes
user_google_emailYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.28.0
    • removedInput schema / properties / comment_content / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / comment_content / type
      Added value: +"string"
    • removedInput schema / properties / comment_id / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / comment_id / type
      Added value: +"string"
  2. Addedv1.0.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the risk profile is covered structurally. The description adds one genuinely useful behavioral caveat (the Drive API cannot anchor comments to arbitrary text, so comments are element-scoped), but it never states what delete actually destroys, whether resolve is reversible, or any auth/scope requirements for a destructive, non-idempotent tool.

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?

One framing sentence followed by a scannable per-action bullet list where each bullet states the requirement up front. The API-anchoring caveat is nested under the action it affects rather than buried in prose, and there is no redundant or filler wording.

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?

An output schema exists, so return values need not be explained, and the multi-action contract plus the anchoring limitation covers most of what is needed to call the tool correctly. What remains missing is any note on read-style access to comments (the list_presentation_comments sibling) and on scope/permission needs for the destructive delete action.

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

Parameters4/5

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

Schema coverage is 0% and the action parameter has no enum in the schema, so the description's action list is doing real work by defining the valid values and mapping each to its required arguments. It does not describe presentation_id or user_google_email, which are left entirely to name inference, keeping this short of a 5.

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 names a specific verb ('Manage') and resource ('comments on a Google Presentation') and then enumerates the five supported operations (create, reply, resolve, update, delete), so an agent knows exactly what capability set is behind the dispatcher. The presentation scope implicitly separates it from manage_document_comment and manage_spreadsheet_comment, but no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear per-action contract by listing the required parameters for each action, which effectively guides which action to pick. However, there is no guidance on when to use this tool versus list_presentation_comments for reading comment threads, no prerequisites or permission notes, and no statement about 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