Skip to main content
Glama

Log Outcome

log_outcome

[Act · writes] Record an outcome by hand. Two kinds. • Outbound (campaign outreach): action sent_request | accepted | replied | no_response with campaign_id and exactly one of person_id or linkedin_url (any profile URL form). The person must be connected to you (in one of your campaigns or segments, engaged with posts you can see in Flux, or pulled by you); anyone else returns not-found with a next_step to pull their profile via linkedin_profile_info. A person outside this campaign's mapped constellation is still logged (with a warning) and get_campaign_stats counts it under unattributed. • Inbound (results your own posting brought in): action inbound_dm | lead | client with profile_id (your tracked profile from list_profiles, whose posts it counts against). No campaign. When the user pastes a LinkedIn DM conversation, pass the whole paste as message_text and set occurred_at to the date of its first message (ISO 8601; omit only if the paste has no date). The sender's linkedin_url is optional and never triggers a paid lookup. Flux matches the outcome to the post that most likely prompted it: post_url if given, else for a lead or client the post already credited for this person's earlier inbound outcome, else the conversation's opening text and timing against your posts from the 30 days before. The result says the method (explicit | inherited | matched | recency | none) and lists up to three candidate posts. When nothing was matched and candidates exist, show them to the user and ask which post it was; then call again with outcome_id and that post_url to correct it. get_inbound_attribution reports which posts bring in DMs, leads and clients. Free — costs 0 credits.

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": {
      "action": "<action>"
    },
    "name": "log_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional free-text note
actionYesOutbound: sent_request | accepted | replied | no_response. Inbound: inbound_dm | lead | client
post_urlNoInbound: URL of your post that prompted it, when the user knows. With outcome_id, corrects an earlier inbound outcome
person_idNopeople.id of the person. Outbound: provide this or linkedin_url. Inbound: optional
outcome_idNoInbound correction: the id of an inbound outcome you logged, with post_url
profile_idNoInbound only, required there: your tracked profile id from list_profiles
campaign_idNoOutbound only, required there: campaign id
occurred_atNoInbound: when it happened, ISO 8601 (for a pasted DM, the first message's date). Defaults to now
linkedin_urlNoLinkedIn profile URL of the person. Outbound: provide this or person_id. Inbound: optional (the sender)
message_textNoInbound: the DM or message text; paste the whole conversation if you have it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"Outreach event: sent_request | accepted | replied | no_response"New value: +"Outbound: sent_request | accepted | replied | no_response. Inbound: inbound_dm | lead | client"
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "sent_request",
      -  "accepted",
      -  "replied",
      -  "no_response"
      -]New value: +[
      +  "sent_request",
      +  "accepted",
      +  "replied",
      +  "no_response",
      +  "inbound_dm",
      +  "lead",
      +  "client"
      +]
    • changedInput schema / properties / campaign_id / description
      Previous value: -"Campaign id"New value: +"Outbound only, required there: campaign id"
    • changedInput schema / properties / linkedin_url / description
      Previous value: -"LinkedIn profile URL of the person you outreached to. Provide this or person_id."New value: +"LinkedIn profile URL of the person. Outbound: provide this or person_id. Inbound: optional (the sender)"
    • addedInput schema / properties / message_text
      Added value: +{
      +  "description": "Inbound: the DM or message text; paste the whole conversation if you have it",
      +  "maxLength": 20000,
      +  "type": "string"
      +}
    • addedInput schema / properties / occurred_at
      Added value: +{
      +  "description": "Inbound: when it happened, ISO 8601 (for a pasted DM, the first message's date). Defaults to now",
      +  "type": "string"
      +}
    • addedInput schema / properties / outcome_id
      Added value: +{
      +  "description": "Inbound correction: the id of an inbound outcome you logged, with post_url",
      +  "format": "uuid",
      +  "type": "string"
      +}
    • changedInput schema / properties / person_id / description
      Previous value: -"people.id of the person you outreached to. Provide this or linkedin_url."New value: +"people.id of the person. Outbound: provide this or linkedin_url. Inbound: optional"
    • addedInput schema / properties / post_url
      Added value: +{
      +  "description": "Inbound: URL of your post that prompted it, when the user knows. With outcome_id, corrects an earlier inbound outcome",
      +  "type": "string"
      +}
    • addedInput schema / properties / profile_id
      Added value: +{
      +  "description": "Inbound only, required there: your tracked profile id from list_profiles",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "campaign_id",
      -  "action"
      -]New value: +[
      +  "action"
      +]
  2. Changed3 schema fields changed
    • addedInput schema / properties / linkedin_url
      Added value: +{
      +  "description": "LinkedIn profile URL of the person you outreached to. Provide this or person_id.",
      +  "type": "string"
      +}
    • changedInput schema / properties / person_id / description
      Previous value: -"people.id — the person you outreached to"New value: +"people.id of the person you outreached to. Provide this or linkedin_url."
    • changedInput schema / required
      Previous value: -[
      -  "campaign_id",
      -  "person_id",
      -  "action"
      -]New value: +[
      +  "campaign_id",
      +  "action"
      +]
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past the annotations: it discloses that the write is free (0 credits), that a person outside the campaign's constellation still logs with a `warning` and is counted as `unattributed`, that a disconnected person yields not-found with a recovery step, and that inbound linkedin_url never triggers a paid lookup. It also explains the attribution fallback chain and the correction flow, none of which the annotations convey.

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-loaded with a tag line and two bulleted mode blocks that mirror the action enum, so the reader can jump to the relevant branch. It is dense and long, and the attribution-matching sentence packs several clauses, but nearly every sentence carries information an agent needs.

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?

For a 10-parameter, two-mode mutation tool with no output schema, the description covers required combinations per mode, error and warning behavior, the matching method values returned (explicit | inherited | matched | recency | none), the candidate list, and the correction path. Nothing essential for a correct first call appears 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?

With 100% schema coverage the baseline is 3, but the description adds real meaning: message_text should carry the whole pasted conversation, occurred_at should be the first message's date for a paste, linkedin_url is optional inbound and free, and post_url paired with outcome_id performs a correction rather than a new log. These are behavioral constraints the schema fields alone do not spell out.

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?

Opens with a specific verb+resource ('Record an outcome by hand') and immediately splits the tool into two clearly named modes, Outbound and Inbound, each with the exact action values they accept. An agent can tell which mode applies from the action set alone, and the description names the downstream reporters (get_campaign_stats, get_inbound_attribution) it relates to.

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 states when each branch applies: outbound requires campaign_id plus exactly one of person_id/linkedin_url, inbound requires profile_id and no campaign. It also gives conditional guidance for edge cases (person not connected → next_step to linkedin_profile_info; unmatched attribution → show candidates and re-call with outcome_id and post_url). Little 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources