Skip to main content
Glama
Sign In
Docs Bridge

Docs Bridge

by dylansantwani
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

slides_rename

Renames a Google Slides presentation by setting a new title for a given deck URL or presentation ID, with an optional account selector for multi-account browsers.

Instructions

Rename a presentation.

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>",
      "title": "<title>"
    },
    "name": "slides_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckYesGoogle Slides URL or presentation id.
titleYes
accountNoWhich 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.

  1. First observedv0.4.0

TDQS

C2.6/5.0
Behavior1/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 provides essentially none. It does not mention required permissions, whether the old title is recoverable, side effects, or the multi-account auth implications introduced by the account parameter.

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?

It is a single front-loaded sentence with no wasted words, but it is undersized for a three-parameter mutation tool. Brevity here reflects under-specification rather than disciplined concision.

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, no output schema, and a mutation operation, the description should say more about permissions, the result of the call, and the account-selection behavior. As written, an agent can guess the action but lacks enough context to call it confidently in multi-account scenarios.

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

Parameters2/5

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

The description adds nothing to the schema, which already documents deck and account reasonably well while leaving title undescribed. With 67% schema coverage, the description should compensate for the remaining gap but makes no attempt to explain title's expected format or any constraints.

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 ('Rename') and resource ('presentation'), making the operation unambiguous. The resource type differentiates it from the docs_* siblings without needing to name them 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?

Usage is only implied by the verb: you rename a presentation when its title needs changing. There are no explicit when-to-use/when-not conditions, no prerequisites, and no mention of alternatives like slides_copy for duplicating under a new name.

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