Skip to main content
Human guide: work with your agent → Inspect one Serper action before starting provider-backed work. Your first result is a verified input and output contract.

​
Provider-specific requirements

Use Serper when you need live Google results fast and broad recall matters more than source-specific extraction. Prefer serper_google_search for:
  • broad web research
  • newsy or changing facts
  • finding a company, person, or topic before deeper enrichment
  • collecting candidate URLs to hand off to extraction tools
Prefer serper_google_maps_search for:
  • local business discovery
  • location-aware company lookups
  • phone, address, rating, website, or CID retrieval
Practical guidance:
  • Start with Serper before heavier browser or extraction workflows when you do not yet know the right destination URL.
  • Treat Serper as a discovery and recall layer, then pass strong hits into structured tools like Firecrawl, Apify, or provider-specific enrichments.
  • Use Maps search when the user cares about storefronts, service areas, offices, or other local entities.
  • Expect live-search variability. If a result is important, validate it with the returned URL or a follow-up fetch.

​
Find an applicable action

Confirm your effective workspace, then search the live catalog:
Search returns candidates. Check the returned provider and operation rather than selecting a similar title automatically.

​
Inspect the selected contract

Replace <returned-tool-id> with the identifier returned by discovery:
These commands do not execute the selected provider action. Read its required inputs, supported access mode, pricing unit, outputs, and limits. A connection does not establish that every action supports BYOK. Follow the provider-specific requirements above and the live action contract.

​
Prepare one reviewed input

Use one authorized record that matches the inspected schema. Preserve its source identity and define the result you will accept. Open the action reference for its payload and response shape. Provider-backed execution can incur usage or external effects. For reusable logic, follow Write Plays. For direct-call recovery, use Tool execution recovery.
Continue only when the workspace, provider, required fields, acceptance rule, and applicable price are understood. Keep unavailable access separate from no-result evidence.