Tool reference

Once connected, the assistant chooses the right tool automatically based on what you ask, so you rarely need to name a tool yourself. This page lists everything it can do, grouped by what each tool is for.

All tools act on the single workspace you authorized when connecting.

Read tools

Use these to inspect the current state of your workspace.

Tool	What it does
`sillage_v2_get_setup_state`	Check what is still left to configure, in one call: the four overall completion flags, plus a diagnostic checklist covering your persona, target accounts, agents, and content, each with a status and a recommended next step.
`sillage_v2_get_persona`	Read your workspace's ideal customer profile (ICP) targeting criteria.
`sillage_v2_read_top_account_list`	List the found accounts in your target list, page by page, and separately list accounts that could not be found.
`sillage_v2_get_top_account_list_status`	Get the size of the target account list and its ingestion status (queued, processing, completed, or failed).
`sillage_v2_get_account_mapping_stage`	Check the processing stage of an account-mapping request.
`sillage_v2_get_contents`	List generated content, or retrieve one item by id.
`sillage_v2_get_content_requests`	List content generation requests, or retrieve one by id.
`sillage_v2_get_agents`	List your agents, or get one by id.
`sillage_v2_get_rate_limit`	Check your remaining request quota for the workspace.

Company mapping tools

Use these to enrich companies and read the results.

Tool	What it does
`sillage_v2_enrich_company`	Look up and enrich a single company by domain, LinkedIn URL, or LinkedIn handle. Returns right away with a `request_id` to poll with `sillage_v2_get_company_mapping`.
`sillage_v2_list_company_mappings`	List the company mappings in your workspace, page by page.
`sillage_v2_get_company_mapping`	Get one company mapping by id, including its matched company and people profiles.

Write tools

Use these to configure targeting and manage agents.

Tool	What it does
`sillage_v2_upsert_persona`	Set or replace your ideal customer profile. This replaces the whole persona, so include every value you want to keep. Warns in the response if job title or location is missing, or if a location could not be matched to a country.
`sillage_v2_add_top_accounts`	Add target accounts to your list. This is additive — existing accounts are kept. Warns in the response if the resulting list falls outside the recommended 5 to 20 accounts.
`sillage_v2_remove_top_accounts`	Remove target accounts from your list. This is destructive.
`sillage_v2_create_agent`	Create a new signal agent. Most agent types require a persona with job title and location set, and at least one target account — job-update agents are exempt. If your workspace is not ready, the request is refused with an explanation of what to set up first.
`sillage_v2_configure_agent`	Update an existing agent's configuration.
`sillage_v2_delete_agent`	Stop an agent and remove it from the workspace. This is destructive.

Watchlist tools

Use these to manage watchlists and their members. A watchlist is a named set of companies or people that an agent can monitor.

Tool	What it does
`sillage_v2_create_watchlist`	Create a new watchlist.
`sillage_v2_list_watchlists`	List the workspace's watchlists.
`sillage_v2_get_watchlist`	Get one watchlist by id.
`sillage_v2_update_watchlist`	Rename a watchlist or update its description.
`sillage_v2_delete_watchlist`	Delete a watchlist. This is destructive.
`sillage_v2_list_watchlist_entities`	List the members (companies or people) of a watchlist.
`sillage_v2_add_watchlist_entities`	Add members to a watchlist.
`sillage_v2_remove_watchlist_entity`	Remove one member from a watchlist.
`sillage_v2_bind_agent_watchlist`	Connect an agent to a watchlist so it monitors those members.

Signal engine tools

Use these to run keyword detection across your target accounts and work with the matches it finds. A run scans each account for your keywords and reports the matches as signals.

Tool	What it does
`sillage_v2_launch_signal_run`	Start a keyword-detection run across your target accounts. Returns right away with a run to follow.
`sillage_v2_get_signal_run`	Follow a run's progress and read its per-account results until it finishes.
`sillage_v2_list_signals`	List the matches found across your runs, one page at a time and optionally filtered by agent.
`sillage_v2_get_signal`	Fetch a single match by its id.
`sillage_v2_add_signal`	Add a match manually, rather than from a run.
`sillage_v2_update_signal`	Update a match.
`sillage_v2_delete_signal`	Delete a match. This is destructive.

Diagnosing your setup

sillage_v2_get_setup_state (and the read-only sillage://setup-state resource, which returns the same data) is the fastest way to see what is missing before doing anything else. Alongside the four overall flags (persona_set, list_uploaded, ingestion_complete, has_contents), the response includes a checklist with one entry for each area of your setup: persona, accounts, agents, and content.

Each checklist entry has:

a status — ok (nothing to do), warning (working, but could be improved), or blocked (needs your attention before things will work);
a plain-language message explaining what is wrong or what to improve;
a recommended next tool to call, when one applies.

For example, a workspace can have persona_set: true (a persona exists) while its checklist entry for persona is warning, because the persona has no job title or location set — the two fields that account mapping and agent creation depend on. blocked is reserved for a persona that does not exist at all (persona_set: false), since that is what actually stops account mapping and agent creation from running. Content is reported explicitly as "feature not enabled, contact Sillage support" when your workspace does not have access to it, rather than looking the same as "nothing generated yet."

Setting up a workspace from scratch

The assistant can run your whole setup. A typical flow:

Check the state with sillage_v2_get_setup_state to see what is missing.
Set the persona with sillage_v2_upsert_persona if none is configured. Targeting is defined here first — job title and location are the two fields that matter most; leaving either one out is flagged in the response and will keep account mapping from running until it is fixed.
Add target accounts with sillage_v2_add_top_accounts. Aim for 5 to 20 accounts — outside that range, the response includes a reminder, but the accounts are added either way.
Wait for ingestion — enrichment runs in the background. The assistant checks sillage_v2_get_top_account_list_status until the status is completed.
Create agents with sillage_v2_create_agent — 3 or more is recommended, mixing job-update, competitor, customer, and keyword-detection agents. Creating most agent types requires a persona with job title and location set and at least one target account (job-update agents are exempt); otherwise the request is refused with an explanation of what to set up first.
Verify with sillage_v2_get_setup_state again to confirm everything is in a good state.

Some tools require the matching workspace feature to be enabled. If a tool reports that access is not allowed, the feature is likely off for your workspace — contact Sillage support to enable it.