Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

apk_teardown_delete_job

Delete an APK teardown job's metadata and results before its retention window expires. The uploaded binary is already removed, so this only purges job records.

Instructions

Delete an apk-teardown job. Purges a job's metadata/result before its normal retention window expires. The uploaded binary is already gone by the time any job reaches a terminal state, so this only ever deletes job metadata, never a binary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYesJob ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the operation is destructive (purges metadata/result), clarifies that the binary is already gone and is never deleted, and explains the retention-window context. It stops short of covering permissions/auth requirements, idempotency, or behavior for jobs that are not yet terminal.

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?

Three sentences, front-loaded with the core action and immediately followed by the two facts an agent most needs (metadata-only scope, binary already gone). No filler or redundancy.

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

Completeness4/5

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

For a single-parameter delete with no output schema, the description covers the essential scope and safety facts. It could be more complete by noting auth/permission requirements or behavior on missing/non-terminal jobs, but the core is sufficient to call the tool correctly.

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?

There is a single required job_id whose semantics are fully documented in the schema (100% coverage). The description adds no meaning beyond that, so the baseline of 3 is appropriate.

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?

The description gives a specific verb (Delete) and resource (an apk-teardown job), and clarifies the scope: it removes a job's metadata/result rather than the uploaded binary. This is enough to distinguish it from siblings like apk_teardown_submit, apk_teardown_job_status, or apk_teardown_diff without opening any schema.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the phrase 'before its normal retention window expires' suggests this is a manual early-purge operation, so the agent can infer it is used when a job should be removed ahead of schedule. However, there is no explicit when-to-use/when-not-to-use guidance or named alternatives among the apk_teardown siblings.

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