Skip to main content
Glama
RPasquale

lightbulb-mcp

by RPasquale
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

salesforce_bulk_ingest_upload

Destructive

Upload bulk data to Salesforce using a domain-agent action. Provide a free-text objective and optional structured inputs to execute the bulk ingest upload under your tenant scope.

Instructions

Run the salesforce domain agent action bulk_ingest_upload.

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

C2.5/5.0
Behavior2/5

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

The annotations indicate destructiveHint=true and readOnlyHint=false, and the description adds that it routes through a dispatcher under JWT/tenant/company scope. However, it does not disclose what side effects occur (e.g., what data is modified or uploaded) or that it is a destructive operation, which would have been valuable context.

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

Conciseness5/5

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

The description is concise and well-structured: a one-sentence purpose, a routing note, and clear parameter definitions. No redundant or fluff content is present.

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?

The description is very minimal for a tool that executes a domain-specific action. It does not explain what 'bulk_ingest_upload' actually does, nor does it clarify the context in which this generic dispatcher should be used versus the more specific connector tools in the sibling list. The lack of any output description (despite an output schema existing) further reduces completeness.

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?

The schema provides no descriptions, so the description carries full weight. It explains 'message' as free-text objective and 'inputs' as optional JSON string of structured inputs, which is moderately helpful but leaves ambiguity about the expected structure or content of these fields.

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

Purpose3/5

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

The description states it runs the 'bulk_ingest_upload' Salesforce domain agent action, which identifies the specific action but does not explain what the action does or how it differs from the sibling tool 'connector_salesforce_bulk_ingest_upload'. The verb 'Run' is clear but the resource ambiguity lowers the score.

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?

No guidance is provided on when to use this tool versus alternatives. Notably, there is a sibling tool named 'connector_salesforce_bulk_ingest_upload' that likely serves a similar purpose, but the description does not mention it or give any selection criteria.

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