Related Servers

Tools target distinct resource+action pairs (campaign, reward, program resource, webhook, participant, analytics, integration, team), and descriptions explicitly cross-reference siblings ('Use growsurf_client_snippets for…') which sharply reduces misselection. The main ambiguity cluster is the six guidance/snippet tools (integration_guide, client_snippets, api_library_snippets, mobile_sdk_guide, embeddable_element_snippet, grsf_config_snippet) plus advisor/eval tools, which an agent could still plausibly confuse, though the descriptions resolve them with effort.

Almost all names share the growsurf_ prefix and a verb_noun snake_case shape (list_campaigns, create_campaign_reward, update_campaign_emails, delete_campaign_webhook), which is very predictable. A handful deviate into noun-phrase or inverted ordering: growsurf_webhook_normalize, growsurf_participant_auth_hash, growsurf_client_snippets, growsurf_mobile_sdk_guide, growsurf_program_design_advisor.

At 63 tools the surface is far beyond a comfortably scoped set, even for a broad platform spanning campaigns, rewards, resources, webhooks, participants, analytics, integrations, and team. Several tools feel like documentation generators rather than operations (integration_guide, mobile_sdk_guide, api_library_snippets, client_snippets, embeddable_element_snippet, grsf_config_snippet, agent_program_creation_eval), inflating the count beyond core API coverage.

Lifecycle coverage is strong: CRUD for campaigns, rewards, program resources, webhooks, and participants, plus analytics, sales/refunds, payout destinations, mobile tokens, and team management — few dead ends for agent workflows. Minor gaps exist, such as no delete_campaign (only status COMPLETE) and no single-participant delete (bulk delete is the only removal path), both of which are workable.