Skip to main content
Glama

sheets_paste_markdown_report

Paste a markdown report into a Google Sheet, converting each line to a row. Optionally clear the target range before writing.

Instructions

Paste a markdown report into a sheet as one line per row.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rangeYesStarting range, e.g. Report!A1
markdownYesMarkdown report content
clearFirstNoClear the target range before writing
spreadsheetIdYes
Behavior2/5

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

With no annotations, the description carries full burden. It states it pastes markdown, but does not disclose how markdown is parsed (e.g., tables, headers), whether it overwrites or appends, or any side effects. The clearFirst parameter is not mentioned in the description.

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

Conciseness3/5

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

The description is a single concise sentence, but it is too brief for the complexity of parsing markdown. It front-loads the action but omits important behavioral details.

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 the tool's complexity (parsing markdown, writing to sheets) and no output schema or annotations, the description is insufficient for an agent to use it confidently. It lacks error handling, return behavior, and details on how the range expands.

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 75%. The description adds the context 'one line per row', implying each line of markdown becomes a row, which aids understanding beyond the schema. However, it does not explain how the range is used or the format of markdown expected.

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 states the action (paste), the resource (markdown report into a sheet), and the behavior (one line per row). It distinguishes from sibling tools like sheets_append_values or sheets_update_values, which handle raw data differently.

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 like sheets_append_values (for appending values) or sheets_clear_values (for clearing). There are no prerequisites, exclusions, or usage context mentioned.

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

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/SandeshKhilari01/google-sheet-mcp'

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