StackFast FractWin Expert Brain

Talent Scout Upsert Campaign Profile

talent_scout_upsert_campaign_profile

Read-only

Create, update, activate, pause, or archive a saved Talent Scout direct-company discovery campaign. Campaigns define company lanes, role lanes, size, geography, comp floor, travel tolerance, negative filters, resume variant, voice anchor, and human-review requirements. Draft/review only; never sends or applies.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No
`status`	No		active
`priority`	No		P1
`tenant_id`	No
`campaign_id`	No
`sqlite_path`	No	Optional local SQLite path for BYOC receipts; hosted cloud calls fail closed instead of reading local files.
`update_mode`	No	Patch preserves omitted fields. Replace is explicit and may reapply defaults.	patch
`voice_anchor`	No
`auth_token_key`	No	Optional wallet/env key name for the tenant Turso auth token. Never pass a raw token.
`radius_minutes`	No
`company_size_max`	No
`company_size_min`	No
`compensation_min`	No
`contact_strategy`	No
`database_url_key`	No	Optional wallet/env key name for the tenant Turso database URL. Never pass a raw URL or secret.
`expanded_regions`	No
`expected_version`	No	Optional optimistic concurrency token from campaign.updated_at. A mismatch fails without writing.
`geography_anchor`	No
`negative_filters`	No
`target_role_lanes`	No
`eligible_countries`	No	Backward-compatible campaign-level work-authorization hint. The stored owner policy still owns the hard country gate.
`minimum_total_comp`	No
`seed_robert_campaign`	No
`target_company_lanes`	No
`tenant_database_type`	No	Optional physical database routing mode. Omit for the default internal StackFast DB; use sovereign_cloud only with wallet-resolved tenant DB credentials.
`acceptable_structures`	No
`resume_variant_strategy`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	No
`public_tool`	Yes
`drafts_never_sends`	No
`no_autonomous_outbound`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 20, 2026

addedInput schema / properties / expected_version

Added value: +{
+  "description": "Optional optimistic concurrency token from campaign.updated_at. A mismatch fails without writing.",
+  "type": "string"
+}

addedInput schema / properties / update_mode

Added value: +{
+  "default": "patch",
+  "description": "Patch preserves omitted fields. Replace is explicit and may reapply defaults.",
+  "enum": [
+    "patch",
+    "replace"
+  ],
+  "type": "string"
+}

Changed1 schema field changedJul 8, 2026

changedInput schema / properties / eligible_countries / description

Previous value: -"Backward-compatible campaign-level work-authorization hint. Candidate policy still owns the hard country gate."New value: +"Backward-compatible campaign-level work-authorization hint. The stored owner policy still owns the hard country gate."

Changed1 schema field changedJul 1, 2026

addedInput schema / properties / eligible_countries

Added value: +{
+  "default": [
+    "US"
+  ],
+  "description": "Backward-compatible campaign-level work-authorization hint. Candidate policy still owns the hard country gate.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed2 schema fields changedJun 25, 2026
- addedInput schema / properties / acceptable_structures
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
- addedInput schema / properties / minimum_total_comp
```
Added value: +{
+  "minimum": 0,
+  "type": "integer"
+}
```

Changed4 schema fields changedJun 25, 2026

addedInput schema / properties / auth_token_key

Added value: +{
+  "description": "Optional wallet/env key name for the tenant Turso auth token. Never pass a raw token.",
+  "type": "string"
+}

addedInput schema / properties / database_url_key

Added value: +{
+  "description": "Optional wallet/env key name for the tenant Turso database URL. Never pass a raw URL or secret.",
+  "type": "string"
+}

addedInput schema / properties / sqlite_path

Added value: +{
+  "description": "Optional local SQLite path for BYOC receipts; hosted cloud calls fail closed instead of reading local files.",
+  "type": "string"
+}

addedInput schema / properties / tenant_database_type

Added value: +{
+  "description": "Optional physical database routing mode. Omit for the default internal StackFast DB; use sovereign_cloud only with wallet-resolved tenant DB credentials.",
+  "enum": [
+    "internal",
+    "sovereign_cloud",
+    "byoc"
+  ],
+  "type": "string"
+}

AddedJun 22, 2026

TDQS

B3.3/5.0

Behavior1/5

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

Annotations declare readOnlyHint=true, but the description claims the tool can 'Create, update, activate, pause, or archive' a campaign—all mutating operations. This is a direct contradiction. The description's 'Draft/review only' nuance does not reconcile saving/updating state with a read-only annotation.

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 three sentences, front-loaded with the tool's core purpose and ends with a sharp behavioral boundary. Every sentence earns its place; no filler or redundant restatement of the tool title.

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?

This is a complex 27-parameter tool with nested objects, yet the description gives only a high-level overview. The read-only annotation contradiction is a critical gap for safe invocation. Although an output schema exists, the description does not explain mutation modes, required vs optional fields, concurrency, or when to use the different routing options.

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

Parameters2/5

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

With only 26% schema description coverage and 27 parameters, the description must compensate, but it only provides category-level hints like 'company lanes, role lanes, size, geography, comp floor...' It adds some conceptual meaning but leaves most parameters—especially routing, auth, concurrency, and update-mode semantics—unexplained.

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 opens with a specific verb and resource: 'Create, update, activate, pause, or archive a saved Talent Scout direct-company discovery campaign.' It clearly lists what the campaign defines and distinguishes this from sibling discovery/application tools by emphasizing saved-campaign configuration and 'Draft/review only.'

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

Usage Guidelines4/5

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

The description gives clear context: this is for configuring/managing saved campaign profiles and explicitly says 'never sends or applies,' which is a useful exclusion. It does not name specific alternative tools or state when to prefer a sibling, but the draft/review framing is enough to guide basic selection.

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

All StackFast FractWin Expert Brain tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?