No user-submitted related servers found.
Scored across 32 tools
Most tools target a clearly distinct resource+action, and descriptions carefully delineate boundaries (e.g. insert_text vs set_text vs replace_text, list_slides vs get_page vs get_presentation). The main friction points are the two escape hatches (batch_update vs raw_request) and the graded read tools, which could still occasionally be mis-selected despite explanatory prose.
The dominant convention is a predictable verb_noun pattern (create_presentation, list_slides, get_page, update_text_style, delete_object, etc.). A few outliers deviate slightly (logout as verb-only, auth_status as noun-first, batch_update/raw_request), but the set remains readable and largely consistent.
At 32 tools the surface is heavy and sits in the range the rubric flags as crowded, though each tool covers a genuinely distinct operation and the domain (Google Slides plus auth, export and comments) is complex. It is borderline over-scoped rather than redundant.
The set covers the full lifecycle: auth/setup/login, reads at three granularities, slide and element creation/mutation/deletion, text, shapes, images, tables, speaker notes, comments, export, and a raw API escape hatch. Documented out-of-scope items (deleting the presentation, changing themes) are Drive/UI operations, not gaps in the Slides surface.