Skip to main content
Glama

HirePulse Company Research

by xyz.gethirepulse.api
OverviewDiscussionsAdmin

Public Company Contacts

extract_company_contacts
Read-only

Published contacts for a company domain from its home, about, contact, team and careers pages: deduplicated emails and LinkedIn, X and GitHub links, plus MX, SPF and DMARC checks (not mailbox verification). $0.01; nothing found is free.

Input Schema

NameRequiredDescriptionDefault
domainYesBare public company domain whose published contact pages and DNS records should be inspected.
contextNoOptional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / anyOf
      Previous value: -[
-  {
-    "properties": {
-      "dmarc": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "domain": {
-        "type": "string"
-      },
-      "email_deliverable": {
-        "type": "boolean"
-      },
-      "emails": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "inferred_email_pattern": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "mx": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "social_links": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "spf": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "status": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "domain",
-      "status"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": true,
-    "properties": {
-      "code": {
-        "minLength": 1,
-        "type": "string"
-      },
-      "status": {
-        "maximum": 599,
-        "minimum": 400,
-        "type": "integer"
-      }
-    },
-    "required": [
-      "status",
-      "code"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "dmarc": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "domain": {
+        "type": "string"
+      },
+      "email_deliverable": {
+        "type": "boolean"
+      },
+      "emails": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "inferred_email_pattern": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "mx": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "sandbox": {
+        "additionalProperties": false,
+        "properties": {
+          "demo_domain": {
+            "const": true,
+            "type": "boolean"
+          },
+          "note": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "demo_domain",
+          "note"
+        ],
+        "type": "object"
+      },
+      "social_links": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "spf": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "status": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "domain",
+      "status"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": true,
+    "properties": {
+      "code": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "status": {
+        "maximum": 599,
+        "minimum": 400,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "status",
+      "code"
+    ],
+    "type": "object"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.",
+  "type": "string"
+}
  3. Changed3 schema fields changed
    • addedOutput schema / anyOf
      Added value: +[
+  {
+    "properties": {
+      "dmarc": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "domain": {
+        "type": "string"
+      },
+      "email_deliverable": {
+        "type": "boolean"
+      },
+      "emails": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "inferred_email_pattern": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "mx": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "social_links": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "spf": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "status": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "domain",
+      "status"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": true,
+    "properties": {
+      "code": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "status": {
+        "maximum": 599,
+        "minimum": 400,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "status",
+      "code"
+    ],
+    "type": "object"
+  }
+]
    • removedOutput schema / properties
      Removed value: -{
-  "dmarc": {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "domain": {
-    "type": "string"
-  },
-  "email_deliverable": {
-    "type": "boolean"
-  },
-  "emails": {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "inferred_email_pattern": {
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "mx": {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "social_links": {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "spf": {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "status": {
-    "type": "string"
-  }
-}
    • removedOutput schema / required
      Removed value: -[
-  "domain",
-  "status"
-]
  4. Changed1 schema field changed
    • addedInput schema / properties / domain / description
      Added value: +"Bare public company domain whose published contact pages and DNS records should be inspected."
  5. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds genuinely useful context beyond them: the pages actually crawled, deduplication behavior, DNS record types inspected, the explicit non-goal (mailbox verification), and the pricing model with a free empty result. It stops short of noting rate limits, latency, or result-cap behavior for an open-world crawl.

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?

A single sentence with no filler, leading with the resource and scope before the outputs, and closing with cost. It is dense — the DNS checks, the non-goal, and the pricing all crowd one sentence — but nothing is superfluous.

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?

An output schema exists, so return values need not be explained, and the description covers scope, data types, caveats, and cost. What's missing is behavioral edge-case guidance (what happens on domains with no contact pages, subdomain input, per-call limits) for an open-world crawl tool.

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

Parameters3/5

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

Schema description coverage is 100% and both parameters are documented there, including the 'bare domain' format and the optional context field, so the schema does the heavy lifting. The description adds no parameter-level detail (no accepted formats, subdomain handling, or IDN/TLD notes) beyond what the schema already states, which is the baseline-3 case.

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 pair (published contacts for a company domain) plus the exact page sources and output kinds (deduplicated emails, LinkedIn/X/GitHub links, MX/SPF/DMARC checks). It also draws a boundary — 'not mailbox verification' — which separates it from anything resembling an email-verification sibling.

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?

The description implies when to use it (you have a bare company domain and want published contact data plus DNS posture) and rules out mailbox verification. But it never names an alternative such as get_company_profile or get_company_open_jobs, nor states prerequisites or exclusions beyond the mailbox caveat, so routing among siblings is left to inference.

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

All HirePulse Company Research 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