Skip to main content
Glama
Eyalm321
by Eyalm321

zernio_create_gmb_place_action

Create action links for Google My Business locations to enable ordering, booking, or shopping directly from your profile.

Instructions

Create a place action link for a Google My Business location (e.g. order food URL, booking URL).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountIdYesThe Zernio Google Business account ID
locationIdYesThe GMB location ID
actionTypeYesThe action type (e.g. 'ORDER', 'BOOK', 'SHOP')
urlYesThe URL for the action link
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states the action ('Create a place action link') without disclosing behavioral traits such as idempotency, side effects, permissions, or success/failure outcomes. Given that this is a write operation, more transparency is expected.

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?

The description is a single, front-loaded sentence of 18 words. Every word serves a purpose, with no redundancy. It efficiently conveys the tool's core function.

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?

The description is adequate for a simple creation tool but lacks details on return values, error scenarios, or lifecycle implications. With no output schema or annotations, agents may miss what is returned after creation. More context, such as the effect on the GMB listing, would improve completeness.

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% with descriptions for all params. The tool description adds value by providing concrete examples for the URL param ('order food URL, booking URL'), clarifying its purpose beyond the generic schema description. This enhances understanding of the 'actionType' and 'url' usage.

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

Purpose5/5

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

The description clearly states the action ('Create a place action link') and the target resource ('Google My Business location'), with concrete examples ('order food URL, booking URL'). This distinguishes it from sibling tools like `zernio_delete_gmb_place_action` and `zernio_get_gmb_place_actions`.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives. While the sibling list implies this is for creation, conditions, prerequisites, or scenarios are not mentioned. The description only states the tool's purpose, leaving usage context to be inferred.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Eyalm321/zernio-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server