Analyze the authenticated organization's advertising and creative performance using Segwise's internal agent. Use this tool to compare performance and trends by app, campaign, ad network, creative, or creative tag and to analyze metrics including spend, impressions, clicks, installs, CTR, CVR, CPI, CPA, ROAS, revenue, and LTV. It can identify winning, declining, or fatigued creatives; explain which hooks, CTAs, visuals, themes, and formats drive results; and recommend what to scale, pause, refresh, or test next. It cannot modify campaigns or generate creatives. It creates a temporary background query job and may save conversation history. It returns a job_id immediately; call get_segwise_query with that exact job_id until the query reports completed or failed. Queries can take several minutes and many status checks. A running status means the query is still executing, not that it failed or has no data. Keep calling get_segwise_query with the exact same job_id, respecting poll_after_seconds. Do not start a duplicate query or stop because repeated checks return running. Give brief progress updates while continuing to poll; do not finish with a still-running answer while polling remains available. Stop polling on completed, failed, execution_deadline, an unrecoverable error, or user cancellation. Retry transient status-check errors with bounded backoff and honor retry delays; do not retry authentication or permission failures. If the host prevents further execution, distinguish that interruption from query failure and preserve the job_id for resumption. organization_id is optional when exactly one organization is available; when multiple organizations are available, present only organization names to the user, map the chosen name to the corresponding organization_id, and retry without asking the user to read or type an ID. Conversation continuity rule: this host chat means the original user's conversation, including work delegated to child agents or subprocesses. Omit conversation_id on the first query for an organization in that conversation. Otherwise, copy the exact conversation_id and organization_id from the latest start or completed result into every later start_segwise_query call for that organization. Follow-ups such as 'How about last month?' reuse those IDs even when the date range, app scope, or topic changes. When delegating, pass both IDs to the child agent or subprocess and require it to use them and return them unchanged with its answer. A new agent, subprocess, or tool invocation does not start a new user conversation. If a follow-up is missing its handle, recover it from the parent or previous tool results before starting the query. Never reuse a handle with another organization or unrelated user conversation. Set new_conversation=true only when the user explicitly requests a fresh conversation; omit conversation_id for that reset.
