DigiAdapt AdTech Intel

Search past AdTech intel

search_intel

Read-only

Search past DigiAdapt briefings (up to a year) for a company, product or keyword, e.g. "PubMatic", "Netflix ads", "identity". Every word must appear in the headline, summary or source. Leave query empty to list everything in the period.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_intel"
  }
}

Input Schema

Name	Required	Description
`days`	No	How far back to look, in days
`limit`	No	Maximum items to return
`query`	No	Company or keywords, e.g. "Magnite"
`category`	No	Limit to one category

Output Schema

Name	Required	Description	Default
`days`	Yes
`items`	Yes
`query`	Yes
`total`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Read-only and closed-world behavior are already declared by annotations, so the description's added value is the matching semantics: every word must appear in headline, summary or source, i.e. AND-style full-text matching. That is genuinely useful beyond the annotations, but it says nothing about ordering, result volume behavior, or cost/latency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: scope first, matching semantics second, the empty-query behavior last. Every sentence carries information an agent needs and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has a full input schema, an output schema, and annotations covering the safety profile, so the description only needs purpose, matching behavior, and the empty-query case — all present. Nothing required to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description earns above baseline by explaining what `query` actually matches against (headline, summary, source) and by clarifying that an empty query enumerates all items in the period — meaning the schema's generic 'Company or keywords' does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (search) plus resource (past DigiAdapt briefings) and bounded scope (up to a year), with concrete example queries. It does not name or contrast with the sibling tools (get_ad_intel, get_adtech_intel, get_market_intel), so a 4 rather than a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear usage context and a useful edge-case rule: 'Leave query empty to list everything in the period,' which tells the agent how to enumerate rather than search. No explicit when-not-to-use or alternative routing is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All DigiAdapt AdTech Intel tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?