Get super connector metadata bulk
get_super_connector_metadata_bulkFetch how and why one or more super connectors were provisioned (roles, qualifying company, investor / public-research / calendar evidence) together with their relevance verdict — summary, relevance_score (1-100 against the workspace's own company), and relevance_band (HIGH/MEDIUM/LOW) — so closeness to the workspace can be judged. Accepts 1..N super connector ids in a single call — always prefer this over calling repeatedly per id.
Use when: When assessing how strong or close one or many super connectors' relationships to the workspace are, given who provisioned them and why. Prefer relevance_band / relevance_score and summary when present; fall back to notes for connectors that have not been scored yet. Use this for both single-id and multi-id lookups.
Behavior: read_only, idempotent
workspace_id / user_id are injected from request headers.
Returns entries[] with fields: super_connector_id provisioning_evidence
IMPORTANT: If the response contains more than one record, always present the options to the user and ask them to choose before taking any follow-up action. Do not act on all results automatically.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| _triggered_by | No | REQUIRED. Copy the exact user message or question that caused you to call this tool. Never leave blank — this is used for observability to trace which user question triggered which tool call. | |
| super_connector_ids | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||