Skip to main content
Glama
RPasquale

lightbulb-mcp

by RPasquale
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

salesforce_bulk_ingest_status

Destructive

Monitor Salesforce bulk ingest progress and retrieve job status using free-text objectives or structured inputs. Get real-time updates on ingestion operations through the domain agent dispatcher.

Instructions

Run the salesforce domain agent action bulk_ingest_status.

Routes through the platform's domain-agent dispatcher under your JWT, tenant, and company scope.

Args: message: Free-text objective for the action. inputs: Optional JSON string of structured inputs for the action.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputsNo{}
messageNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • removedInput schema / properties / arguments
      Removed value: -{
-  "default": "{}",
-  "title": "Arguments",
-  "type": "string"
-}
    • addedInput schema / properties / inputs
      Added value: +{
+  "default": "{}",
+  "title": "Inputs",
+  "type": "string"
+}
    • addedInput schema / properties / message
      Added value: +{
+  "default": "",
+  "title": "Message",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

D1.7/5.0
Behavior2/5

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

The description adds only that the action routes through the platform's domain-agent dispatcher under JWT/tenant/company scope. It does not disclose what the status action observes, what side effects occur, or why the annotations mark it as destructiveHint=true; given that annotation, this is a significant transparency gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and structured, but brevity here comes from omitting core information rather than from tight, informative writing. The routing sentence provides context, not tool semantics, and no sentence explains what the action does or how to invoke it correctly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Even with an output schema present, the description lacks when-to-use context, input semantics, and the relationship to the bulk ingest lifecycle. With a destructiveHint=true annotation and many overlapping sibling tools, this is insufficient for an agent to confidently select and call the tool.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must explain the parameters, but it only labels message as 'Free-text objective' and inputs as 'Optional JSON string'. It does not describe expected content, format, or how these map to a bulk ingest status request.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description only says to run the action `bulk_ingest_status` and gives routing details; it never states what that action actually does, such as checking the status of a Salesforce bulk ingest job. This is essentially a tautology of the tool name and does not differentiate the tool from siblings like salesforce_bulk_ingest_results or salesforce_bulk_query_status.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus the many related salesforce bulk tools (create, upload, close, results, query_status). It does not mention prerequisites, polling semantics, job ID requirements, or any alternatives.

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

Deploy Server

Other Tools