Skip to main content
Glama
Sign In
google-docs-mcp

google-docs-mcp

by dbuxton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

docs_list

Locate Google Docs in Drive by optional search query, filtering results by title or content to get a list of relevant documents.

Instructions

List Google Docs from Drive, optionally filtered by a search query.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "docs_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results (default 20)
queryNoOptional search terms (searches title and content)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

There are no annotations, so the description carries the burden of behavioral disclosure. 'List' implies a read-only, non-mutating operation, and the mention of 'optionally filtered by a search query' adds useful behavior. However, it does not explicitly state that no side effects occur, the scope of results, or how results are ordered.

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?

A single, clear sentence that is front-loaded with the action and resource. Every word earns its place with no redundant filler.

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 tool is relatively simple with two optional parameters and an output schema that covers return values. However, with no annotations and no usage guidance relative to siblings, the description leaves the agent to infer when this tool should be used and what the results actually contain.

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%, so the schema already documents both parameters. The description mentions an optional search query but adds no detail beyond the schema, such as query syntax or what fields are searched.

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 action ('List') and the resource ('Google Docs from Drive'), with an optional filter. It is clear enough to distinguish from sibling mutation and retrieval tools, though it does not explicitly name a sibling alternative.

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 given about when to choose docs_list versus docs_get, docs_create, or other sibling tools. The usage context is only implied by the verb 'List' and the presence of an optional query filter.

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