Skip to main content
Glama

Public Tenders (EU, US, UK, AU)

kadi_bence/ted-tenders-scraper

kadi_bence--ted-tenders-scraper
Destructive

This tool calls the Actor "kadi_bence/ted-tenders-scraper" and retrieves its output results. Actor description: Open EU public tenders and contract award winners from TED, all EU/EEA countries. Optional: who won the buyer's previous similar contract, and for how much. Filters: keywords, countries, CPV, NUTS, deadline, value. Returns title, buyer, value, winners, deadline, URL. Default: 20. $1.50/1K.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kadi_bence--ted-tenders-scraper"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpvCodesNoCommon Procurement Vocabulary codes, e.g. 72000000 (IT services) or 45000000 (construction work). Sub-categories are included automatically: 72000000 also returns 72100000, 72260000 ... You can also type a short prefix like 72.
keywordsNoWords or phrases searched in the full notice text, in any EU language, e.g. 'software', 'cloud computing', 'Reinigung'. Several lines = any of them (OR). Notices are mostly in the buyer's language, so add local words. Use short terms, not sentences. Leave empty to get all notices that match the other filters.
waitSecsNoMax seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget.
buyerNameNoWords in the contracting authority's name, e.g. 'Charité' or 'Stadt München'. Accents don't matter.
countriesNoCountry of the contracting authority. Leave empty for all countries. Example values: ["DE"]
nutsCodesNoRegions where the contract is performed, e.g. DE2 (Bavaria), FR10 (Paris area), ITC4 (Lombardy). Sub-regions are included.
maxResultsNoStop after this many notices. 0 = no limit (there is no 15,000 cap). The default without input (API, MCP and AI-agent calls) is 20. Example values: 20
expertQueryNoA raw TED expert-search query, e.g. buyer-country=DEU AND classification-cpv=72000000 AND publication-date>=today(-7). Replaces ALL filters above. Test it at ted.europa.eu/en/search/expert-search. Newest first unless you add SORT BY.
monitorNameNoKeeps separate 'already seen' lists for different schedules. Example values: "default"default
noticeTypesNoLeave empty for all types. Pick 'Contract notice' for open calls you can still bid on, 'Contract award' for who won and for how much. Example values: ["contract_notice"]
publishedToNoLast publication date (YYYY-MM-DD).
deadlineAfterNoOnly tenders you can still bid on: notices whose tender (or request-to-participate) deadline is on or after this date. Tip: also accepts 'today' or '+14 days'.
publishedFromNoFirst publication date (YYYY-MM-DD).
onlyNewNoticesNoRemember returned notices and output only NEW ones on the next runs with the same search. Ideal for a daily schedule: you only pay for new notices.
maxEstimatedValueNoSame currency rule as above.
minEstimatedValueNoEstimated contract value of the whole procedure, in the notice's own currency (most notices are in EUR). Notices without a published value are excluded when you set this.
proxyConfigurationNoNot needed: TED is an open-data API. Example values: {"useApifyProxy":false}
publishedWithinDaysNoe.g. 7 for the last week, 1 for yesterday and today. Leave empty to use the date range below (or no date limit). Example values: 7
includePreviousAwardNoFor each open tender, look up the buyer's earlier contract awards (last 5 years, same CPV division) and add the most similar one: winners, awarded value, date and link. Shows who you are likely competing against and at what price. One extra TED search per buyer, so runs take a bit longer.

Output Schema

NameRequiredDescriptionDefault
tipNoAdvisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key
runIdYesActor run ID
statsNoRun statistics
statusYesRun status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED
actorIdYesStable Apify Actor ID from the run record
summaryYesPast-tense summary of the run state
exitCodeNoActor process exit code; populated for terminal states (especially FAILED)
nextStepYesOne primary follow-up action with identifiers interpolated
storagesYesDataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
actorNameNo"username/actor-name"
startedAtNoISO timestamp when the run started
finishedAtNoISO timestamp when the run finished (terminal states only)
statusMessageNoPass-through from Apify run.statusMessage
apifyConsoleUrlNoPersonalized Apify Console link to the run; present only for Console sessions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
  3. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
  4. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
  5. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
  6. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
  7. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
  8. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
  9. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
  10. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
  11. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
  12. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
  13. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
  14. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
  15. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
  16. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
  17. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
  18. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
  19. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
  20. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
  21. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
  22. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
  23. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
  24. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
  25. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
  26. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
  27. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
  28. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
  29. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
  30. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
  31. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
  32. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
  33. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
  34. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
  35. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
  36. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
  37. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
  38. Changed5 schema fields changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / awardedCurrency / type
      Previous value: -"null"New value: +[
      +  "null",
      +  "string"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / awardedValue / type
      Previous value: -"null"New value: +[
      +  "null",
      +  "number"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / deadline / type
      Previous value: -"string"New value: +[
      +  "null",
      +  "string"
      +]
    • addedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / winnerCountries / items / type
      Added value: +"string"
    • addedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / winners / items / type
      Added value: +"string"
  39. Changed1 schema field changed
    • addedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema
      Added value: +{
      +  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
      +  "properties": {
      +    "awardedCurrency": {
      +      "type": "null"
      +    },
      +    "awardedValue": {
      +      "type": "null"
      +    },
      +    "buyerCity": {
      +      "type": "string"
      +    },
      +    "buyerCountry": {
      +      "type": "string"
      +    },
      +    "buyerName": {
      +      "type": "string"
      +    },
      +    "contractNature": {
      +      "type": "string"
      +    },
      +    "cpvCodes": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "currency": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "deadline": {
      +      "type": "string"
      +    },
      +    "description": {
      +      "type": "string"
      +    },
      +    "estimatedValue": {
      +      "type": [
      +        "null",
      +        "number"
      +      ]
      +    },
      +    "language": {
      +      "type": "string"
      +    },
      +    "lotsCount": {
      +      "type": "number"
      +    },
      +    "mainCpv": {
      +      "type": "string"
      +    },
      +    "mainCpvLabel": {
      +      "type": "string"
      +    },
      +    "noticeType": {
      +      "type": "string"
      +    },
      +    "noticeTypeCode": {
      +      "type": "string"
      +    },
      +    "pdfUrl": {
      +      "type": "string"
      +    },
      +    "placeOfPerformanceCountries": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "placeOfPerformanceNuts": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "procedureType": {
      +      "type": "string"
      +    },
      +    "publicationDate": {
      +      "type": "string"
      +    },
      +    "publicationNumber": {
      +      "type": "string"
      +    },
      +    "scrapedAt": {
      +      "type": "string"
      +    },
      +    "title": {
      +      "type": "string"
      +    },
      +    "titleLanguage": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    },
      +    "winnerCountries": {
      +      "items": {},
      +      "type": "array"
      +    },
      +    "winners": {
      +      "items": {},
      +      "type": "array"
      +    },
      +    "winnersOmitted": {
      +      "type": "number"
      +    },
      +    "xmlUrl": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  40. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true, so the description doesn't need to re-establish that this is an external, side-effecting run. It adds genuinely useful behavior beyond them: it is a paid Actor run at '$1.50/1K', it returns a default of 20 results, and it enumerates what comes back (title, buyer, value, winners, deadline, URL). It stops short of describing run time or the wait/polling behavior, which is documented only in the waitSecs parameter.

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

Conciseness4/5

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

The definition is compact and front-loads the resource and scope before filters, returns, and price. The opening boilerplate sentence about 'calls the Actor... and retrieves its output results' is generic filler, but nothing else is wasteful.

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?

With 19 optional parameters, an output schema, and full schema descriptions, the definition covers scope, main filter families, return fields, and cost well enough to call the tool. It omits notable modes such as incremental monitoring (onlyNewNotices/monitorName) and the expertQuery escape hatch, which are meaningful capabilities an agent would not learn from the description alone.

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 description coverage is 100%, so the schema already explains CPV prefixes, NUTS sub-regions, expert query syntax, date formats, and monitoring mode in detail. The description only mirrors the filter list (keywords, countries, CPV, NUTS, deadline, value) without adding syntax or interaction rules, 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.

Purpose4/5

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

The description gives a specific verb and resource: it runs the 'kadi_bence/ted-tenders-scraper' Actor and returns EU public tender and contract-award data from TED across EU/EEA countries. The scope ('Open EU public tenders... from TED') implicitly separates it from the non-EU siblings gov-tenders-scraper and sam-gov-scraper, but it never names them, so sibling differentiation is left to inference.

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?

It states the domain (EU/EEA TED notices), the available filter families, and the default of 20 results, which implies when the tool is appropriate. However, it never says when to prefer a sibling scraper or when this tool is the wrong choice, and it doesn't flag the monitoring/onlyNewNotices workflow as a distinct usage mode.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.