Docs Bridge

Overview Schema Source Related Servers Discussions Admin

slides_copy

Copy a Google Slides presentation and assign it a new title, selecting the signed-in account if the deck belongs to a different profile.

Instructions

Make a copy of a presentation with a new title.

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": {
      "deck": "<deck>"
    },
    "name": "slides_copy"
  }
}

Input Schema

Name	Required	Description
`deck`	Yes	Google Slides URL or presentation id.
`title`	No
`account`	No	Which signed-in Google account to use: an index as in /u/N/ URLs (0 = first account) or an email address. Omit for the browser default. Use this for presentations owned by a second (e.g. school) account.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Oct 18, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and falls short. It does not say where the copy is placed, whether sharing/permissions carry over, what identifier is returned, or whether the source deck is unaffected. For a mutation tool with zero annotation coverage this is a meaningful gap.

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?

A single compact sentence with the action and the key qualifier front-loaded. Nothing is wasted, though the brevity is partly under-specification rather than discipline.

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?

With no annotations and no output schema, the description should compensate but does not. It omits the return value (presumably a new presentation id), the copy's destination, and any cross-account implications of the 'account' parameter.

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 67%: 'deck' and 'account' are documented in the schema, while 'title' has no description. The phrase 'with a new title' does clarify that title names the resulting copy rather than the source, adding modest value, but it gives no format or length guidance.

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 states a specific verb and resource ('Make a copy of a presentation') and adds the scope qualifier 'with a new title'. It is immediately clear what the tool does, though it never differentiates itself from siblings like slides_create or docs_copy.

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?

There is no guidance on when to use this versus slides_create (a fresh deck) or slides_rename (retitling an existing deck). No prerequisites, no mention of the account parameter's relevance to cross-account copying.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.