Skip to main content
Glama

Marketingburos

by nl.marketingburos
OverviewDiscussionsAdmin

search_agencies

Search Dutch marketing agencies by specialisms, target_industry (the client vertical the agency serves), city, B2B/B2C, company size, budget band and an optional radius (near_city = any Dutch city, or near_lat/near_lon, always combined with within_km in kilometres). specialisms filters strictly against the taxonomy; unrecognised terms are echoed in filters.specialisms.unmatched (all unknown → 0 results + hint). budget_band only excludes agencies with a known conflicting rate (see filters.budget_band.note). Returns up to 20 ranked agencies with slug (use in get_agency_profile), public trade name (name, plus legal_name when the statutory name differs), a 1-line rationale in Dutch, and totalMatched (hits before the limit). Ranking ignores what an agency pays (never pay-to-rank). Read the categories://list resource for valid values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoExact office city of the agency. For 'near a city' use near_city + within_km instead.
limitNoMax results (1-20, default 10).
near_latNoCenter latitude of a radius search (alternative to near_city). Requires near_lon + within_km.
near_lonNoCenter longitude of a radius search (alternative to near_city). Requires near_lat + within_km.
near_cityNoCenter of a radius search: any Dutch city name. Requires within_km.
within_kmNoRadius in kilometres around near_city or near_lat/near_lon (max 250). Ignored without an origin; near_* is ignored without within_km.
budget_bandNoBuyer's budget in EUR. Only excludes agencies whose known rates conflict; most agencies have no known rate.
specialismsNoUp to 5 specialism slugs from categories://list (e.g. 'seo', 'branding'). Unknown terms are echoed back in filters.specialisms.unmatched.
target_industryNoClient vertical the agency serves (e.g. the buyer's own industry). Not the agency's own sector.
company_size_bandNoSize of the buyer's company (employees); matches agencies that target that segment.
client_orientationNob2b or b2c focus of the agency.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / budget_band / description
      Added value: +"Buyer's budget in EUR. Only excludes agencies whose known rates conflict; most agencies have no known rate."
    • addedInput schema / properties / city / description
      Added value: +"Exact office city of the agency. For 'near a city' use near_city + within_km instead."
    • addedInput schema / properties / client_orientation / description
      Added value: +"b2b or b2c focus of the agency."
    • addedInput schema / properties / company_size_band / description
      Added value: +"Size of the buyer's company (employees); matches agencies that target that segment."
    • addedInput schema / properties / limit / description
      Added value: +"Max results (1-20, default 10)."
    • addedInput schema / properties / near_city / description
      Added value: +"Center of a radius search: any Dutch city name. Requires within_km."
    • addedInput schema / properties / near_lat / description
      Added value: +"Center latitude of a radius search (alternative to near_city). Requires near_lon + within_km."
    • addedInput schema / properties / near_lon / description
      Added value: +"Center longitude of a radius search (alternative to near_city). Requires near_lat + within_km."
    • addedInput schema / properties / specialisms / description
      Added value: +"Up to 5 specialism slugs from categories://list (e.g. 'seo', 'branding'). Unknown terms are echoed back in filters.specialisms.unmatched."
    • addedInput schema / properties / target_industry / description
      Added value: +"Client vertical the agency serves (e.g. the buyer's own industry). Not the agency's own sector."
    • addedInput schema / properties / within_km / description
      Added value: +"Radius in kilometres around near_city or near_lat/near_lon (max 250). Ignored without an origin; near_* is ignored without within_km."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full load. It discloses restricted specialism taxonomy with unmatched-term echoing, the budget_band non-blocking behavior, the 20-result cap, totalMatched, non-influenceable ranking, and the return rationale in Dutch. This is far beyond basic 'search' semantics.

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

Conciseness4/5

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

The description is dense rather than concise, but each sentence contributes a key behavioral note or parameter nuance. It front-loads the search function and enumerates filters before tying return fields together. It is longer than strictly necessary, but no sentence is wasted.

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?

For an 11-parameter tool with no output schema, this description is remarkably complete: it documents the return fields, the ranking rule, the taxonomy constraint, the budget_band exception, the radius requirement, and the link to get_agency_profile. An agent could safely invoke the tool without access to any structured schema.

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

Parameters5/5

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

Despite 100% schema coverage, the description adds meaning beyond the JSON schema fields: specialisms must come from categories://list taxonomy and unknown terms are echoed in filters, budget_band only excludes conflicting known rates, target_industry is buyer verticals, and near_* only works with within_km. These intended semantics materially affect agent behavior.

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?

Uses a specific verb (

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?

Provides context for when to use the tool and how: it's a discovery search returning slugs, and directs the agent to get_agency_profile for profile details. It also tells the agent to read categories://list for valid specialisms. It does not, however, explicitly state when not to use this tool and when to prefer find_agency, so it stops one step short of an explicit when-not/alternative.

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

All Marketingburos toolsInspect
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