Engagemii AI Visibility Data

Create a data account

data_signup

Create a free Engagemii data account, or sign in to an existing one, with just an email address. There is no password: we send a one-click sign-in link (valid 30 days) to the address. When the user clicks it they are signed in and the address is verified, which activates the account's API key (edk_...). The key is then shown at https://engagemii.com/aeo/data/portal/api and unlocks search_companies and data_records. Use the email address the user gives you.

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": {
      "email": "<email>"
    },
    "name": "data_signup"
  }
}

Input Schema

Name	Required	Description	Default
`email`	Yes	The user's email address. The sign-in link is sent here.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 27, 2026

removedInput schema / properties / company_name
```
Removed value: -{
-  "type": "string"
-}
```

addedInput schema / properties / email / description

Added value: +"The user's email address. The sign-in link is sent here."

removedInput schema / properties / license_accepted

Removed value: -{
-  "description": "Whether the user has explicitly accepted the data license",
-  "type": "boolean"
-}

removedInput schema / properties / password

Removed value: -{
-  "description": "8+ characters, chosen by the user",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "email",
-  "password",
-  "company_name",
-  "license_accepted"
-]New value: +[
+  "email"
+]

Changed1 schema field changedSep 28, 2026

changedInput schema / properties / license_accepted / description

Previous value: -"true ONLY if the user explicitly accepted the license"New value: +"Whether the user has explicitly accepted the data license"

First observedSep 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Substantially exceeds the annotations: it discloses the passwordless magic-link mechanism, the 30-day link validity, the asynchronous side effect (an email is sent to the address), that clicking it verifies the address and activates the API key, and where the key surfaces (the portal URL). These are exactly the side effects an agent needs since openWorldHint/idempotentHint=false alone say little.

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?

Four tight sentences, front-loaded with the action and outcome and followed by the mechanism, the consequence (key activation), the key location, and the parameter constraint. No sentence is redundant.

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

Completeness4/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 carries the return burden and mostly discharges it by explaining the link email and the key appearing at a portal URL. It stops short of stating what the immediate tool response looks like (e.g., a confirmation/'check your inbox' payload), which is the only residual gap.

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 the baseline is 3; the description earns one step more by instructing the agent to use the address supplied by the user rather than fabricating one, and by tying the parameter to its effect ('the sign-in link is sent here').

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 first sentence names a specific verb and resource ('Create a free Engagemii data account, or sign in to an existing one') and the last identifies what it unlocks ('search_companies and data_records'), which cleanly separates it from the data-reading siblings. An agent knows exactly which capability this provides without opening the schema.

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?

It states the precondition clearly - the resulting edk_ key 'unlocks search_companies and data_records' - so the agent can infer this is the gate before using those tools. The closing line 'Use the email address the user gives you' gives practical guidance, but there is no explicit when-not-to-use case or named alternative for already-authenticated scenarios.

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

All Engagemii AI Visibility Data 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?