Skip to main content
Glama

AIsa Go-To-Market

by one.aisa
OverviewDiscussionsAdmin

Email Lookup

post_waveinflu_email_lookup
Read-onlyIdempotent

Looks up the contact email for one Instagram, TikTok, or YouTube creator from a profile URL. Pass profile_url; the response returns the parsed platform, the normalized profile_url, and an email object {status, value}. A not_found status (with value null) is a normal result, not an error, and is still billed as one valid lookup. Handles one creator per call. To assemble a creator list first, use Similar Creators or AI Search — each match already includes an email for most creators; use this endpoint for the ones that come back null.

Usage-based billing; Default request estimate: $0.001991 USD (not a fixed price). Declared unit rate: $0.001991 USD per email_lookup_point. Account-specific pricing and final settlement may differ.

Input Schema

NameRequiredDescriptionDefault
bodyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / body
      Added value: +{
+  "properties": {
+    "profile_url": {
+      "description": "Instagram, TikTok, or YouTube creator profile URL.",
+      "example": "https://www.instagram.com/onkimia/",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • removedInput schema / properties / profile_url
      Removed value: -{
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "body"
+]
  2. Changed3 schema fields changed
    • removedInput schema / properties / profile_url / description
      Removed value: -"Instagram, TikTok, or YouTube creator profile URL."
    • removedInput schema / properties / profile_url / example
      Removed value: -"https://www.instagram.com/onkimia/"
    • changedInput schema / required
      Previous value: -[
-  "profile_url"
-]New value: +[]
  3. Changed3 schema fields changed
    • addedInput schema / properties / profile_url / description
      Added value: +"Instagram, TikTok, or YouTube creator profile URL."
    • addedInput schema / properties / profile_url / example
      Added value: +"https://www.instagram.com/onkimia/"
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "profile_url"
+]
  4. Changed3 schema fields changed
    • removedInput schema / properties / profile_url / description
      Removed value: -"Instagram, TikTok, or YouTube creator profile URL."
    • removedInput schema / properties / profile_url / example
      Removed value: -"https://www.instagram.com/onkimia/"
    • changedInput schema / required
      Previous value: -[
-  "profile_url"
-]New value: +[]
  5. Changed3 schema fields changed
    • addedInput schema / properties / profile_url
      Added value: +{
+  "description": "Instagram, TikTok, or YouTube creator profile URL.",
+  "example": "https://www.instagram.com/onkimia/",
+  "type": "string"
+}
    • removedInput schema / properties / url
      Removed value: -{
-  "description": "TikTok, Instagram, or YouTube creator profile URL.",
-  "example": "https://www.instagram.com/onkimia/",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "url"
-]New value: +[
+  "profile_url"
+]
  6. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: a `not_found` status with null value is a normal outcome rather than an error, and it is still billed as one valid lookup, plus the per-lookup pricing unit. It does not mention auth requirements or rate limits, so it stops short of a 5.

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?

Front-loads the core action and payload, then layers response shape, error semantics, and routing in descending order of importance. The embedded pricing comment block is machine-generated noise, but the prose itself is tight with 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?

An output schema exists, so return values were already documented, yet the description still surfaces the two things an agent actually needs to reason about: the `not_found` case is normal and billable, and one creator is handled per call. Combined with the sibling routing, nothing needed to call this 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 description coverage is 0% at the top level (the single nested `body.profile_url`), so the description must compensate, and it does: it tells the agent to pass `profile_url` and constrains the accepted values to Instagram, TikTok, or YouTube profile URLs, matching the schema example. It adds no syntax rules (e.g., trailing slash or handle-only input), so it is not fully exhaustive.

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?

States a specific verb and resource — looks up the contact email for exactly one Instagram/TikTok/YouTube creator from a profile URL — and names the sibling alternatives (Similar Creators, AI Search) it is not. An agent can distinguish this from post_waveinflu_ai_search or post_waveinflu_similar_creators without opening any schema.

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

Usage Guidelines5/5

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

Explicit routing guidance: use the list-producing endpoints first to assemble a creator list, then call this endpoint for the creators whose `email` came back null. The one-creator-per-call constraint is stated outright, which prevents batching misuse.

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

All AIsa Go-To-Market 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