Related Servers

Most tools have clearly distinct resource-action pairs, but a few overlaps exist: get_login_branding and get_login_appearance both describe login page appearance settings, and get_project_overview vs get_tenant_schema both provide project-level structural information. The help-related trio (ask_admin_help, search_admin_help, get_admin_help_article) also requires careful reading to distinguish, though their descriptions do clarify the different access modes.

The vast majority of tool names follow a snake_case verb_noun pattern (list_entries, create_master_record, update_contact_form). Minor inconsistencies include patch_project_content_locales mixing 'patch' with the more common 'update', get_funnel_status whose description says it 'reconfigures' rather than simply fetches, and long compound verbs like migrate_field_to_master_reference and rename_master_record_slug. Overall the pattern is predictable and readable.

With 52 tools, the surface is overwhelming for an agent. While the platform covers a broad domain, many tools are highly granular (e.g., separate login branding vs appearance, three separate help tools, three agent-run lifecycle tools) and could be consolidated. This clearly exceeds the 25+ threshold for 'too many' tools.

Core content workflows are well covered: entry lifecycle (create/list/get/update, save_revision, publish), master data CRUD, contact forms, media upload, and blueprints. However, there are notable gaps: no delete_entry or unpublish operation, no media delete/update, no master record delete, and no list_agent_runs. These missing lifecycle operations will require workarounds or human intervention, making the surface incomplete for fully autonomous agent workflows.