Skip to main content
Glama
deenesjakoruzh
Unstructured-IO

Unstructured API MCP Server

Official
by Unstructured-IO
OverviewSchemaRelated ServersScoreDiscussions
Remote

delete_source_connector

Remove a source connector from the Unstructured API MCP Server by specifying its ID to manage data integration sources.

Instructions

Delete a source connector.

Args:
    source_id: ID of the source connector to delete

Returns:
    String containing the result of the deletion

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
source_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • uns_mcp/connectors/source/source_tool.py:158-174 (handler)
    The handler function that executes the deletion of a source connector using the unstructured client API.
    async def delete_source_connector(ctx: Context, source_id: str) -> str:
    """Delete a source connector.

    Args:
        source_id: ID of the source connector to delete

    Returns:
        String containing the result of the deletion
    """
    client = ctx.request_context.lifespan_context.client

    try:
        await client.sources.delete_source_async(request=DeleteSourceRequest(source_id=source_id))
        return f"Source Connector with ID {source_id} deleted successfully"
    except Exception as e:
        return f"Error deleting source connector: {str(e)}"
  • uns_mcp/connectors/source/__init__.py:15-15 (registration)
    Registers the delete_source_connector function as an MCP tool.
    mcp.tool()(delete_source_connector)
  • uns_mcp/connectors/source/__init__.py:4-7 (registration)
    Imports the delete_source_connector function for registration.
        create_source_connector,
    delete_source_connector,
    update_source_connector,
)

Tool Definition Quality

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states this is a deletion operation, implying it's destructive, but doesn't disclose critical behavioral traits like whether deletion is permanent, requires specific permissions, affects associated data (e.g., workflows or jobs), or has rate limits. For a destructive tool with zero annotation coverage, this is a significant gap.

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 front-loaded with the core purpose in the first sentence, followed by structured Arg and Return sections that are clear and efficient. Every sentence earns its place without redundancy, making it appropriately sized for the tool's complexity.

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

Completeness3/5

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

Given the tool has an output schema (implied by 'Returns' statement), the description doesn't need to detail return values. However, as a destructive operation with no annotations and minimal behavioral disclosure, it's incomplete—lacking info on side effects, prerequisites, or error handling. It meets a baseline but has clear gaps for safe usage.

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?

The description adds meaningful context for the single parameter 'source_id' by specifying it's 'ID of the source connector to delete', which clarifies its role beyond the schema's basic title 'Source Id'. With 0% schema description coverage and only one parameter, this adequately compensates, though it could note format or sourcing details.

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

Purpose4/5

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

The description clearly states the verb ('Delete') and resource ('a source connector'), making the purpose unambiguous. However, it doesn't differentiate from its sibling 'delete_destination_connector' or 'delete_workflow', which would require specifying what makes a source connector distinct from those other deletable entities.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'delete_destination_connector' or 'delete_workflow', nor does it mention prerequisites (e.g., ensuring the connector isn't in use) or consequences. It simply states what the tool does without contextual usage information.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Unstructured-IO/UNS-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server