Skip to main content
Glama

AIsa Go-To-Market

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.

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": {
      "body": "<body>"
    },
    "name": "post_waveinflu_email_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / body / required
      Added value: +[
      +  "profile_url"
      +]
  2. 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"
      +]
  3. 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: +[]
  4. 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"
      +]
  5. 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: +[]
  6. 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"
      +]
  7. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds important context: output includes `{status, value}`, `not_found` is normal rather than an error, and it is still billed as a valid lookup. Billing and status semantics are transparent and do not contradict annotations.

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 front-loaded with purpose and input, then moves to output behavior, billing, and alternatives. It is fairly efficient, though the pricing block and some output detail make it longer than strictly necessary.

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?

Given a single-parameter tool with an output schema, the description covers the key call behavior, normal `not_found` outcome, billing implication, one-creator limit, and sibling alternatives. An agent has enough information to invoke it correctly.

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 0%, but the description compensates by naming `profile_url` as the required input and clarifying it is a creator profile URL for Instagram, TikTok, or YouTube. It adds meaningful semantics beyond the bare schema, though URL format details remain mostly in the schema example.

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 contact email for one Instagram/TikTok/YouTube creator from a profile URL. It also distinguishes the one-creator scope from batch alternatives, so an agent can identify it against sibling tools.

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?

Explicitly says to pass `profile_url`, handles one creator per call, and directs agents assembling lists to Similar Creators or AI Search, using this endpoint only for nulls. That gives clear when-to-use and when-not-to-use guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources