Skip to main content
Glama
Sign In

Nas.com

by com.nas
OverviewDiscussionsAdmin

Search Magic Audience Geolocations

search_magic_audience_geolocations
Read-only

Search Meta Ads geolocation targets for Magic Audience. Before offering this action or requesting its inputs, check business permissions. FREE businesses cannot use this tool, regardless of individual feature rows. Call check_business_tool_access before collecting inputs. Show any grace-period warning and verified resubscribe link before continuing, and never proceed when access is blocked.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "communityId": "<communityId>"
    },
    "name": "search_magic_audience_geolocations"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
limitNoMaximum number of results to return.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / communityId / description
      Added value: +"Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of results to return."
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavioral context beyond that: FREE-tier businesses are blocked regardless of feature rows, and a grace-period warning plus verified resubscribe link must be surfaced. It says nothing about result shape or pagination, but that is a minor gap given the annotations.

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

Conciseness3/5

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

The purpose statement is correctly front-loaded, but the permission paragraph is repetitive: "Before offering this action or requesting its inputs, check business permissions" and "Call check_business_tool_access before collecting inputs" say substantially the same thing. Tightening to one gating sentence would lose nothing.

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

Completeness3/5

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

With no output schema, the description is the only place an agent could learn what a geolocation target looks like or how results are capped, and it does not say. It is complete on the access-gating dimension, which is clearly the author's priority, but incomplete on what the call actually returns for a 3-parameter search tool.

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

Parameters2/5

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

Schema coverage is 67%: limit and communityId are documented in the schema, but q has no description anywhere, and the description does not clarify what q matches (geolocation name, country code, city?). The only added signal is the phrase "geolocation targets," which hints at the domain but adds no real parameter meaning.

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?

"Search Meta Ads geolocation targets for Magic Audience" gives a specific verb (search) and a specific resource (Meta Ads geolocation targets), scoped to Magic Audience. It is clearly distinguishable from mutation siblings like create_magic_audience_campaign, though it does not explicitly contrast with the other search_* tools such as search_custom_domains.

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?

Strong prerequisite guidance: check business permissions, call check_business_tool_access before collecting inputs, and never proceed when access is blocked. However, it gives no guidance on choosing this tool over sibling search tools, so the when-to-use coverage is one-sided.

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

All Nas.com 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