Sumble

Tools 37

• Get Account Information

  Check your API key and account status. Free (no credits used). Further account details are available at https://sumble.com/account

• Get My Company Profile

  Get your company's positioning and target-account intelligence profile. Call this before researching or prioritizing accounts, preparing calls, or drafting outreach. It combines your team's own sales guidance with Sumble's inferred ICP facets. Treat the team-written guidance as authoritative and the inferred facets as supporting evidence. Your team manages its guidance at https://sumble.com/account/alert-prompts. Free (no credits used). The response is stable for the session, so fetch it once and reuse it for follow-up work.

• List Contact Lists

  List the user's contact lists (people lists). Use `GetContactList` afterward to retrieve the people in a specific list. Always share each list URL so the user can open it in Sumble. Costs 1 credit per returned list.

• Get Contact List

  Get one contact list and its people. Fetch a list by id after calling `ListContactLists`. Contact information is present only for enriched contacts. Always share the list URL and the relevant person URLs with the user. Each person carries a `url` (their Sumble profile) and a `linkedin_url`: link the person by their Sumble `url`, and treat LinkedIn as secondary, offered alongside rather than instead. Costs 1 credit per returned person. A list of more than 500 people is refused and nothing is charged unless `allow_expensive_query` is true. Confirm the spend with the user before setting it, once per call: a confirmation never carries over to any other call.

• Create Contact List

  Create a new contact list (people list). Use `AddContactsToList` to populate it afterward. Always share the list URL so the user can open it in Sumble. Workflow when a user wants to build a people list: 1. Call `FindMatchAndEnrichPeople` to get Sumble person IDs. 2. Call `CreateContactList` to make the list. 3. Call `AddContactsToList` with the person IDs. If you already have Sumble person IDs (from a prior API call), skip step 1 and use those IDs directly. Always ask the user for the list name. If you have a good guess, you can suggest it in the prompt.

• Add Contacts To List

  Add people to an existing contact list. Duplicates are silently skipped. Always share the list URL so the user can open it in Sumble. Workflow when a user provides names or LinkedIn URLs: 1. Call `FindMatchAndEnrichPeople` to resolve them to Sumble person IDs. 2. Call `AddContactsToList` with the matched IDs (use the "id" field from each result). If you already have Sumble person IDs (from a prior API call), pass them directly as people_ids.

• Search Documentation

  Search Sumble's official product documentation. Use this first when the user asks how Sumble itself works. It searches each published page as one document and returns the best matching page paths, titles, URLs, and excerpts. Pass a result's `path` to `GetDocumentationPage` when the complete Markdown is needed. Link the user to the result's `url` when citing it. Free (no credits used).

• List Documentation

  List every page of Sumble's official product documentation. Use this whenever the user asks how Sumble itself works, rather than asking for data out of Sumble. That covers: getting started and core concepts; what Sumble's data is and where it comes from; the filter reference; the paid REST API and its endpoints; MCP; the web app (search, org pages, teams, people, lists, signals, feed, alerts, exports, credits); the Slack agent; enterprise services (Enrich, Signals, account scoring); setup and configuration (users and SSO, Salesforce, HubSpot, Snowflake, Databricks, blob storage, Slack alerts); pricing and plans; and trust and security. Prefer this over a web search for anything Sumble documents. These are the same pages published at docs.sumble.com, and they are authoritative. Pages come back in the order the documentation's own navigation lists them. Read the listing, then fetch the page you need with `GetDocumentationPage`, passing its `path` verbatim. Free (no credits used).

• Get Documentation Page

  Read one page of Sumble's official product documentation. Call `ListDocumentation` first and pass a `path` from its results verbatim. Paths are exact, and cannot be guessed from a page's title or its published URL. An unrecognized path is an error, so do not invent one: list the pages again and pick from those. Link the user to the returned `url` when citing the page. Do not construct a documentation URL yourself. Free (no credits used).

• List Organization Lists

  List the user's organization lists, which contain their accounts. Use `GetOrganizationList` afterward to retrieve one list's organizations. Always share the relevant list URLs so the user can open them in Sumble. Each list has a type: "group" or "user". A "group" list is the user's territory, synced from their employer's CRM or territory management system. Questions about "my territory" or "my accounts" map to the group list. Lists the user built themselves have type "user". Costs 1 credit per returned list.

• Get Organization List

  Get one saved organization list and its organizations by list_id. `account_status` is the CRM relationship between the org and the calling account: 'customer' for a customer account, 'prospect' for an account tracked in CRM but not marked as a customer, or 'not_in_crm' when no CRM record exists. `crm_url` links directly to the CRM record when unambiguous. `crm_url` is null when there is no CRM record or multiple ambiguous CRM matches. `account_status` is null only when the calling account has no linked CRM seat (Salesforce or HubSpot), meaning it is not configured for CRM data. Typically used after calling `ListOrganizationLists`. It is not filterable. Always share the list URL and the relevant Sumble profile URLs with the user. Costs 1 credit per returned item. A list of more than 500 organizations is refused and nothing is charged unless `allow_expensive_query` is true. Confirm the spend with the user before setting it, once per call: a confirmation never carries over to any other call. `GetOrganizationList` only retrieves saved lists. Use `FindMatchAndEnrichOrganizations` for a general organization search. Its `organizations_list` filter limits that search to one of the user's lists.

• Create Organization List

  Create a new organization list. Use `AddOrganizationsToList` to populate it afterward. Always share the list URL with the user so they can view it in the dashboard. Workflow when a user provides company names or URLs: 1. Call `FindMatchAndEnrichOrganizations` to resolve them to Sumble IDs. 2. Call `CreateOrganizationList` to make the list. 3. Call `AddOrganizationsToList` with the matched IDs. If you already have Sumble org IDs (from a SQL query, FindMatchAndEnrichOrganizations, or another API call), skip step 1 and use those IDs directly. Always ask the user for the list name to use. If you have a good guess for the name, you can suggest it in the prompt. Do not create a new list just to change an existing list's name. Use `RenameOrganizationList` so the list keeps its id, URL, and organizations.