Optmyzr

Executes a routine-management capability. A routine is a saved configuration or process that monitors or performs recurring work on the user's behalf. First use describe_capability to identify the capability and obtain its parameters, scope, confirmation requirements, and result contract. Include the target accountId and platform in every call.

create_routine

CATEGORY: READ. Describes the capabilities available through other functions and what each function can handle. Use when: - You need the exact 'parameters' a capability accepts, its valid values, or its columns → capability='...' - You are unsure which capability covers a user need → query='shopping product spend' - You want everything one domain offers → domain='<domain>' Do NOT use when: - You already looked up this exact capability earlier in this conversation and already know its inputs — call the domain function directly instead of looking it up again. Execution constraints: - No arguments → the compact index of every available capability (id + one-line gloss + domain). - Read-only; needs no account context.

describe_capability

Executes a capability scoped to one ad account, or to a portfolio where the capability supports it (platform=portfolio). Reads are served from the account's own ad platform, linked analytics properties, and Optmyzr's analysis; each capability's card lists its supported platforms, and new data sources are added without changing this function. Raw platform-native queries — today a GAQL SELECT statement executed against the Google Ads API — are available through a capability discoverable via describe_capability. First use describe_capability to identify the capability and obtain its parameters, supported platforms, behavior, and result contract. Include the target accountId and platform in every call.

get_platform_data

Reads Optmyzr routine data. A routine is a saved configuration or process that monitors or performs recurring work on the user's behalf. First use describe_capability to identify the capability and obtain its parameters, scope, behavior, and result contract.

get_routine_data

Reads Optmyzr workspace data. The workspace is scoped to the Optmyzr user or organization rather than one advertising account. First use describe_capability to identify the capability and obtain its parameters, behavior, and result contract.

get_workspace_data

CATEGORY: WRITE. Changes anything in an ad account or optmyzr entities through a reviewable change request. Pick what to do with 'operation'; operation-specific inputs go inside 'parameters'. First use describe_capability to identify the operation and obtain its parameters, behavior, and result contract.

make_changes

CATEGORY: READ. One search over Optmyzr's product knowledge: help articles (how-to, troubleshooting, navigation) AND the feature/tool directory (which Optmyzr tool fits a need). Both are searched with the same query; narrow with 'source' when only one is wanted. Use when: - user needs guidance, troubleshooting, or has product-related questions - user asks how to find or reach an Optmyzr page or feature - user wants to discover which Optmyzr tool fits their need Do NOT use when: - you need to know what data this server can fetch → describe_capability Execution constraints: - Results describe Optmyzr product features in general — they are NOT the list of what this server can do; describe_capability is. If a feature has no corresponding capability here, present it as something the user can do in the Optmyzr UI. - accountId + platform are optional — when provided, feature suggestions are tailored to that account. - A feature result carries a direct link into the Optmyzr tool — include it when the user needs to reach a page, and reproduce it exactly; never invent a feature name or a URL.

search_optmyzr_knowledge