Why Don't Google Search Operators (site:, before:, after:) Work in My Agent's Web Search?

Last updated: May 14, 2026

Your agent's built-in Web Search doesn't route through Google — it routes through Exa, Parallel, or Firecrawl (whichever you've set as the Fetch Provider) or the model's native web search. None of those providers parse Google-style operators like site:, after:YYYY-MM-DD, before:YYYY-MM-DD, or quoted phrases. To actually filter by domain or date, rephrase the search in natural language, add the provider's MCP directly so you can pass its native filter parameters, or use a domain-specific MCP that has real filters.

Symptoms

  • You wrote a prompt that tells the agent to search for something like site:instagram.com/p/ "brand strategy" after:2026-05-13 and the agent dutifully runs it.

  • The results ignore the date range, include results from the wrong domains, or treat your quoted phrase as loose keywords.

  • The agent doesn't warn you that the operators were ignored — it just returns whatever the provider sent back.

  • You burn credits running the same agent over and over hoping the operators will start working.

Why This Happens

The built-in Web Search tool on agents is a thin wrapper around an external search provider. Under the hood it calls one of:

  • Exa — AI/neural search

  • Parallel — AI-powered web search

  • Firecrawl — web data API with search

  • The model's native web search (for OpenAI and Anthropic models that support it)

Your query string is passed to the provider verbatim. No Google-style operator parsing happens anywhere in the path. Each provider has its own search API with its own filter parameters — site:, after:, before:, and quoted-phrase semantics are Google conventions and don't apply.

How to Fix It

Option 1: Rephrase the search in natural language (simplest)

The built-in providers are AI search engines — they understand intent, not operators. Drop the operators and describe what you want as a sentence. Be explicit about the domain and time window in plain English.

Example prompts you can try right now:

  • "Search the web for Instagram posts about brand strategy published in the last 24 hours. Only return links from instagram.com."

  • "Find articles published after May 13, 2026 about brand strategy. Prefer results from instagram.com."

To make this automatic, tell your agent in the same chat:

Update your system prompt to include this instruction:
When you use the built-in Web Search tool, never include Google-style
operators (site:, after:, before:, quoted phrases). They are not parsed
by the underlying provider. Instead, write the query as a natural-language
sentence and state any domain or date constraint in words. If a strict
filter is required, ask the user whether to use a provider MCP (Exa /
Parallel / Firecrawl) or a domain-specific MCP instead.

Or: "Create a skill called 'web-search-rules' with the above behavior."

If your agent has the self-updating toggle turned off, add it manually in the system prompt field.

Option 2: Add the provider's MCP for native filter parameters

If you need strict domain or date filtering, the built-in tool is not the right layer — it doesn't expose the provider's structured filters. Add the underlying provider's MCP to your agent so it can call the provider's tool with the real parameter names.

To add an MCP tool to your agent, see How to Give Your Agent Access to an Integration. The provider MCPs are documented at Exa, Parallel, and Firecrawl.

Each provider has its own filter parameters. Common ones:

  • Exa — includeDomains, excludeDomains, startPublishedDate, endPublishedDate, category

  • Parallel — include_domains, exclude_domains, max_age_seconds, objective

  • Firecrawl — date_range_start, date_range_end, country, source-type filters (web / news / images)

Example prompts you can try right now:

  • "Use the Exa search tool. Set query to "brand strategy", includeDomains to ["instagram.com"], and startPublishedDate to "2026-05-13"."

  • "Use the Firecrawl search tool with query "brand strategy", date_range_start "2026-05-13", and limit results to instagram.com."

To make this automatic, tell your agent in the same chat:

Update your system prompt to include this instruction:
When the user asks for results filtered by domain or date, prefer the
Exa search tool with includeDomains and startPublishedDate over the
built-in Web Search. Pass filter values as structured parameters,
never as Google operators in the query string.

Heads up: Exa is an AI-based search engine, so even with strict parameters its results can drift slightly. For absolute precision on a single site, use Option 3.

Option 3: Use a domain-specific MCP for real, source-side filters

When you're searching one specific platform (Instagram, LinkedIn, Reddit, YouTube, GitHub, etc.), skip web search entirely and use that platform's MCP. The filters are applied by the platform itself, which is the only way to get truly authoritative results.

For example, the Instagram MCP's get_hashtag_posts tool natively supports a newer_than time filter (e.g. "1 day", "7 days") — a real time filter, applied by Instagram, not a Google operator hack.

Example prompts you can try right now:

  • "Use the Instagram tool to get hashtag posts for #brandstrategy with newer_than set to "1 day"."

  • "Use the GitHub tool to search repositories about brand strategy created after 2026-05-13."

To make this automatic, tell your agent in the same chat:

Update your system prompt to include this instruction:
When the user asks for posts, repos, videos, or records from a specific
platform, always prefer that platform's MCP tool over the built-in Web
Search. Use the platform's native time and domain filters instead of
operators in a query string.

How Do I Know It Worked?

  • Your search returns results that actually match the date range and domain you specified, not a random mix.

  • The agent's reasoning shows it called the provider's tool with structured parameters (includeDomains, startPublishedDate, etc.), not a query string with operators.

  • Run-to-run results are consistent for the same filter values.

Where to Change the Fetch Provider

The Fetch Provider for the built-in Web Search is set per agent. Open the agent's configuration panel, find the Web Search tool entry, click the three-dot menu, and pick Exa, Parallel, or Firecrawl. This only changes which provider receives your query — none of them parse Google operators, so changing providers alone won't fix the operator issue. You still need one of the three options above.

Still Need Help?

If this didn't resolve your issue, reach out to support at support@gumloop.com.

Related Docs