Skip to main content
Glama
r28ai

Chief of Staff

by r28ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

gdrive_comments_list

Read-onlyIdempotent

List comments on a Google Drive file by ID, specifying required fields to return exact details like content, author, timestamps, and replies.

Instructions

List a file's comments. The fields parameter is required — for example comments(id,content,author,createdTime,resolved).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsYesRequired. The `fields` parameter must be set. To return the exact fields you need, see Return specific fields. Example: `comments(id,content,author,createdTime,modifiedTime,resolved,replies(id,content,author,createdTime,action))`.
fileIdYesThe ID of the file.
pageSizeNoThe maximum number of comments to return. The service may return fewer than this value. If unspecified, at most 20 comments will be returned. The maximum value is 100; values above 100 will be coerced to 100.
pageTokenNoThe token for continuing a previous list request on the next page. This should be set to the value of `nextPageToken` from the previous response.
includeDeletedNoWhether to include deleted comments. Deleted comments will not include their original content.
startModifiedTimeNoThe minimum value of 'modifiedTime' for the result comments (RFC 3339 date-time).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true. The description adds no behavioral context beyond repeating the required 'fields' parameter, which is already documented in the schema. No mention of pagination behavior, rate limits, or auth requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero waste, with the required parameter front-loaded. Efficient and direct, though the example could be more complete.

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

Completeness3/5

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

The description covers the mandatory parameter but neglects the other optional parameters (pageSize, pageToken, includeDeleted, startModifiedTime) that could affect usage. For a list tool with no output schema and rich schema documentation, it's adequate but incomplete.

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 description coverage is 100%, so the schema fully documents all parameters including the 'fields' requirement. The description repeats the 'fields' requirement, adding no syntax or format details beyond what the schema provides, which is the baseline for high schema coverage.

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 'comments' scoped to a file. It doesn't explicitly distinguish from siblings, but the 'file's comments' scope is specific enough that the agent can identify it as the Drive comments-list tool.

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 on when to use this tool vs alternatives like gdrive_files_list or other comment-related operations. The description assumes the agent already knows it needs comments and just needs the fields parameter.

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