Apify Public Data & Leads

TED European Tender Search

ted_eu_tender_search

Read-only

Search European public tenders by keyword, buyer, country, or CPV code to identify bid opportunities, deadlines, and estimated values from official TED notices.

Instructions

Search official Tenders Electronic Daily notices by keywords, contracting authority, country, CPV code and publication date. Returns buyers, deadlines, estimated values, classifications and direct TED documents.

Behavioral Transparency:

Execution: Network call executed synchronously in the cloud via Apify Actor 'captainhandsome/ted-eu-tender-search'.
Side Effects: Reads public sources and creates a billed Actor run and dataset on your Apify account.
Authentication: Requires APIFY_TOKEN environment variable.
Latency & Limits: Typical run duration is 10-45 seconds; output is capped by max_results.

Usage Guidelines:

When to use: Use for European public-procurement discovery, bid monitoring, buyer research and CPV market analysis.
When NOT to use: Do not use for US grants (use 'grants_gov_opportunity_search') or completed US federal awards (use 'usaspending_contracts').
Named alternatives: Use 'grants_gov_opportunity_search' for US funding opportunities or 'usaspending_contracts' for awarded US contracts.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cpv_code`	No	Eight-digit Common Procurement Vocabulary code.
`keywords`	No	Words or phrase to match in TED notice titles.
`language`	No	Three-letter TED language code.	eng
`buyer_name`	No	Text to match in contracting authority names.
`max_results`	No	Maximum tender notices to return.
`buyer_country`	No	ISO alpha-3 buyer country code, for example DEU or FRA.
`sort_direction`	No	Newest or oldest publication date first.	desc
`publication_date_to`	No	Latest publication date, YYYY-MM-DD.
`publication_date_from`	No	Earliest publication date, YYYY-MM-DD.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`run`	No
`error`	No
`status`	Yes
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed40 schema fields changedv1.1.0Sep 15, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / error
```
Added value: +{
+  "type": "object"
+}
```
- changedOutput schema / properties / results / items / properties / buyer_countries / description
```
Previous value: -"Buyer country codes."New value: +"Pipe-separated ISO alpha-3 buyer country codes."
```
- addedOutput schema / properties / results / items / properties / buyer_countries / title
```
Added value: +"Buyer Countries"
```
- changedOutput schema / properties / results / items / properties / buyer_countries / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / buyer_names / description
```
Previous value: -"Contracting authority names."New value: +"Pipe-separated contracting authority names."
```
- addedOutput schema / properties / results / items / properties / buyer_names / title
```
Added value: +"Buyer Names"
```
- changedOutput schema / properties / results / items / properties / buyer_names / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / cpv_codes / description
```
Previous value: -"Main CPV codes."New value: +"Pipe-separated main Common Procurement Vocabulary codes."
```
- addedOutput schema / properties / results / items / properties / cpv_codes / title
```
Added value: +"CPV Codes"
```
- changedOutput schema / properties / results / items / properties / cpv_codes / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / currency / description
```
Previous value: -"Estimated-value currency."New value: +"Currency code for the estimated procedure value."
```
- addedOutput schema / properties / results / items / properties / currency / title
```
Added value: +"Currency"
```
- changedOutput schema / properties / results / items / properties / currency / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / deadlines / description
```
Previous value: -"Tender receipt deadlines."New value: +"Pipe-separated tender receipt deadline dates."
```
- addedOutput schema / properties / results / items / properties / deadlines / title
```
Added value: +"Deadlines"
```
- changedOutput schema / properties / results / items / properties / deadlines / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / description / description
```
Previous value: -"Lot descriptions."New value: +"Pipe-separated lot descriptions in the preferred available language."
```
- addedOutput schema / properties / results / items / properties / description / title
```
Added value: +"Description"
```
- changedOutput schema / properties / results / items / properties / description / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / estimated_value / description
```
Previous value: -"Estimated procedure value."New value: +"Estimated procedure value as a number when supplied."
```
- addedOutput schema / properties / results / items / properties / estimated_value / title
```
Added value: +"Estimated Value"
```
- changedOutput schema / properties / results / items / properties / estimated_value / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / notice_url / description
```
Previous value: -"Canonical TED notice page."New value: +"Canonical TED notice detail URL."
```
- addedOutput schema / properties / results / items / properties / notice_url / title
```
Added value: +"Notice URL"
```
- changedOutput schema / properties / results / items / properties / notice_url / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / pdf_url / description
```
Previous value: -"Direct preferred-language PDF."New value: +"Direct preferred-language TED PDF URL."
```
- addedOutput schema / properties / results / items / properties / pdf_url / title
```
Added value: +"PDF URL"
```
- changedOutput schema / properties / results / items / properties / pdf_url / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / publication_date / description
```
Previous value: -"TED publication date."New value: +"TED publication date normalized to YYYY-MM-DD."
```
- addedOutput schema / properties / results / items / properties / publication_date / title
```
Added value: +"Publication Date"
```
- changedOutput schema / properties / results / items / properties / publication_date / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- addedOutput schema / properties / results / items / properties / publication_number / title
```
Added value: +"Publication Number"
```
- changedOutput schema / properties / results / items / properties / publication_number / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / title / description
```
Previous value: -"Notice title."New value: +"Notice title in the preferred available language."
```
- addedOutput schema / properties / results / items / properties / title / title
```
Added value: +"Notice Title"
```
- changedOutput schema / properties / results / items / properties / title / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- addedOutput schema / properties / run
```
Added value: +{
+  "type": "object"
+}
```
- addedOutput schema / properties / status
```
Added value: +{
+  "enum": [
+    "success",
+    "empty_unverified",
+    "partial",
+    "error"
+  ],
+  "type": "string"
+}
```
- changedOutput schema / required
```
Previous value: -[
-  "results"
-]New value: +[
+  "results",
+  "status"
+]
```
Addedv1.0.13Sep 14, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond annotations, the description discloses execution model (synchronous cloud Actor), side effects (billed Actor run and dataset), authentication requirement (APIFY_TOKEN), and latency limits (10-45 seconds, max_results cap). This meaningfully augments the annotations without contradicting them.

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 well-structured with focused sections: a one-sentence summary, a behavioral transparency block, and a usage-guideline block. Every sentence provides actionable information, and key facts are front-loaded.

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

Completeness5/5

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

For a complex 9-parameter tool, the description covers when to use it, when not to use it, authentication, side effects, latency, limits, and output content. Combined with the full schema and output schema, nothing essential for correct invocation is missing.

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?

Schema coverage is 100%, so the schema already documents every parameter in detail. The description does not clarify additional meaning beyond the schema, but because baseline 3 is appropriate when the schema fully covers parameter semantics, it neither adds nor detracts.

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 — 'Search official Tenders Electronic Daily notices' — and enumerates the distinct search dimensions (keywords, contracting authority, country, CPV code, publication date. It also states what is returned, making the tool's purpose unmistakable even among 30 sibling tools.

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

Usage Guidelines5/5

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

The Usage Guidelines section explicitly provides explicit when-to-use scenarios and explicit exclusion cases, naming two sibling tools (grants_gov_opportunity_search and usaspending_contracts) for US grants and awarded contracts. This is the highest level of guidance an agent could receive.

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